WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: PDFs: Logical Reading Order and Tags

for

From: Moore,Michael (Accessibility) (HHSC)
Date: Jun 1, 2016 7:11AM

In my experience these are the most important items.

1. The tag order should match the reading order. Unless something has changed recently the major screen readers follow the tag order for reading content.

2. Table structure - the tag structure for a table must be correct, including table headers and header and id's if necessary. Without this much of the meaning for the tables is lost.

3. List structure - the same thing is true here too. If single lists are broken into multiple lists this makes it more difficult to understand the content when it read using a screen reader.

4. Heading structure. Are headings at logical levels within the context of the document and are they nested appropriately.

The actual tag used may or may not be important as long as it maps to the correct structure. This can be controlled in either InDesign or Acrobat Pro - this is best set up in InDesign that way the final tags don't look so strange.

Some good tests with the screen reader.

Run a headings list. The headings list should provide a good outline of the document.

Scan the lists. Are the lists complete and nested correctly.

Scan the tables - use table reading commands to test that headers are being reported correctly.

Read by paragraph. Does what the screen reader thinks is a complete paragraph match what visually exists in the document or are there extra breaks.

Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Alan Zaitchik
Sent: Wednesday, June 01, 2016 7:38 AM
To: <EMAIL REMOVED>
Subject: [WebAIM] PDFs: Logical Reading Order and Tags

When we get a PDF generated out of InDesign the tags are usually non-HTML5-standard tags in a jumbled order. Yet often the logical reading order is fine, or can easily be fixed using the Acrobat tool for doing so. Testing in a screen reader like JAWS or NVDA seems to yield a pass as well- the content is read in the correct order.
How important is it that the tags themselves be (1) rearranged to match the logical reading order, and (2) thoroughly reworked to use only HTML5 standard tags?
I imagine this turns on the question whether there are AT tools other than JAWS and NVDA that depend on these tags being standard and reordered.
Thanks,
A