A11y

ABBYY FineReader Amazement and Disappointment

by

I’ve spent much of the past three days giving myself a crash-course in ABBYY FineReader on my (Windows) work laptop, and have been really impressed with its speed, accuracy, and ability to greatly streamline the process of making scanned PDFs searchable and accessible. After testing with the demo,I ended up getting approval to purchase a license for work, and I’m looking forward to giving it a lot of use – oddly, this seemingly tedious work of processing PDFs of scanned academic articles to produce good quality PDF/UA accessible PDFs (or Word docs, or other formats) is the kind of task that my geeky self really gets into.

Since I’m also working a lot with PDFs of old scanned documents for the Norwescon historical archives project, tonight after getting home I downloaded the trial of the Mac version, fully intending to buy a copy for myself.

I’m glad I tried the trial before buying.

It’s a much nicer UI on the Mac than on Windows (no surprise there), and what it does, it does well. Unfortunately, it does quite a bit less — most notably, it’s missing the part of the Windows version that I’ve spent the most time in: the OCR Editor.

On Windows, after doing an OCR scan, you can go through all the recognized text, correct any OCR errors, adjust the formatting of the OCR’d text, even to the point of using styles to designate headers so that the final output has the proper tagging for accessible navigation. (Yes, it still takes a little work in Acrobat to really fine-tune things, but ABBYY makes the entire process much easier, faster, and far more accurate than Acrobat’s rather sad excuse for OCR processing.)

On the Mac, while you can do a lot to set up what gets OCRd (designating areas to process or ignore, marking areas as text or graphic, etc.), there’s no way to check the results or do any other post-processing. All you can do is export the file. And while ABBYY’s OCR processing is extremely impressive, it’s still not perfect, especially (as is expected) with older documents with lower quality scan images. The missing OCR Editor capability is a major bummer, and I’m much less likely to be tossing them any of my own money after all.

And most distressingly, this missing feature was called out in a review of the software by PC Magazine…nearly 10 years ago, when ABBYY first released a Mac version of the FineReader software. If it’s been 10 years and this major feature still isn’t there? My guess — though I’d love to be proven wrong — is that it’s simply not going to happen.

Pity, that.

Disability Pride Flag

by

While we’re just halfway through Pride month, July is Disability Pride Month, and in preparation for this year, I’ve created a high resolution version of Ann Magill’s Disability Pride Flag, which she released into the public domain. I have also created a brighter variant that may be more suitable in some situations.

A muted black field with a diagonal stripe running from the top left to bottom right in muted green, blue, white, yellow, and red.

You can snag the images from this blog post, or you can download the 175 KB Disability Pride Flag .zip file, which includes both the standard and bright variants as high-resolution (2000×3000 pixel) .png, .svg, and .pdf files, along with the Affinity Designer source files I created.

A black field with a diagonal stripe running from the top left to bottom right in green, blue, white, yellow, and red.

An explanation of the design and the meaning of the colors, from Ann:

I and several people with visually triggered disabilities (some of whom wished to remain anonymous) have collaborated to come up with this new design, shown above. The colors have been muted and rearranged to reduce eye strain, and each stripe also has a slightly different level of brightness (brightest in the center and darkening outward), so that even those with some form of color blindness can distinguish the stripes.

And in case you’re wondering, here’s the flag’s symbolism:

Having All Six “Standard” Flag Colors: signifying that Disability Community is pan-national, spanning borders between states and nations.

The Black Field: Mourning and rage for victims of ableist violence and abuse

The Diagonal Band: “Cutting across” the walls and barriers that separate the disabled from normate society, also light and creativity cutting through the darkness

The White Stripe: Invisible and Undiagnosed Disabilities

The Red Stripe: Physical Disabilities

The Gold Stripe: Neurodivergence

The Blue Stripe: Psychiatric Disabilities

The Green Stripe: Sensory Disabilities

Download link: DisabilityPrideFlag.zip (175 KB)

iA Presenter and Headings

by

I’m quite curious about iA Presenter (a new Markdown-focused presentation creation app), so I downloaded the 14-day trial.

And it is immediately driving me up the wall that in the sample/instructional presentation that loads by default, the creators are repeatedly misusing headings to create the style for their demonstration slides.

The iA Presenter window as first opened to the demo presentation. The Markdown code for the content begins with an H1 followed by an H4. The next slide begins with an H3 that is followed by an H2.

The cover slide starts with an H1 and then immediately jumps to an H4, presumably because they wanted the visual distinction between the larger text of the title and the notably smaller text of what’s being used as a subtitle. But that skips two levels of headings.

The second slide (and many other slides) starts with an H3 that is immediately followed by an H2. Consistently, slide after slide, it’s an H3 followed by an H2. Again, this appears to be done for the visual presentation, as it results in the smaller-text headline over the larger-text headline. But that means that the headings are all out of order and don’t create a consistent outline to indicate the structure of the document.

And this sort of thing continues throughout the entire demo presentation.

Not only is this generally sloppy, but it’s an accessibility issue: When headings are skipped, users of assistive technology like screen readers have to try to figure out from context whether the headings have actually been skipped, or if they’re they exist but haven’t been tagged properly, or if they’re being presented out of order. When the document outline is out of order, it makes it much more difficult to navigate through and build a coherent mental picture of the final document.

I haven’t gotten as far as looking to see how iA Presenter does with its output (Is the HTML it generates standards compliant? Are the PDFs it generates properly tagged for accessibility)? But even if it exported perfect HTML or ideally tagged PDFs, the content will have accessibility issues because the designers are prioritizing style over substance. And with this as their demo, many people using the app will likely follow their lead.

And that’s a shame. Because on first blush, it’s a gorgeous app with some extremely good advice on how to conceptualize and plan better presentations and some great templates. All criticisms aside, I’m still looking forward to experimenting with it. But the abuse of headings and lack of concern for reasonable document structure is not giving a very good first impression.

Read more