Today's webinar drove home the point that making a PDF accessible goes beyond clicking Adobe's built-in Accessibility Checker. To effectively use screen readers and other assistive devices, the structure and reading order of a document has to be be logical ordered and explicitly defined.
The View tags panel displays each html structure tag - line breaks, column breaks, table headers, row and cells and images in the document. "Walk the tag list", one tag after the other, observing which text or image element highlights. This check to see if the assistive device will bring the right information to the listener in the right order.
It's easy to THINK your document is accessible when it's not because:
- the "Accessiblity checker" will report missing alt (explanatory) tags, but not faulty tagging.
- the View > "Read out loud" feature is not a screen reader, so it can't read structures such as tables. This feature does not satisfy 508 requirements for accessibility.
- Word's paragraph tags don't break the text blocks into elements and can be misread.