PDF Reading Order
What It Is
Reading order is the sequence in which assistive technology walks through a PDF's content. It lives in the tag tree (the structure tree, walked depth-first) and is separate from the visual placement of glyphs on the page. A two-column newsletter might visually open with a headline across the top, drop into the left column, then jump to the right column -- and the tag tree must spell that sequence out explicitly, because PDF page coordinates do not imply order[1].
Why It Matters
When the tag tree is auto-generated from raw content-stream order (roughly left-to-right, top-to-bottom across the page), a two-column layout linearises as line-1-left + line-1-right + line-2-left + line-2-right -- interleaved nonsense for a screen-reader user. The same failure mode puts a sidebar callout into the middle of a body paragraph, drops a caption in before the figure it describes, or folds a running footer into the sentence above it. The content is present; the sequence is scrambled, and a sighted reviewer scrolling the page will not see the defect because their eye reconstructs the layout visually.
How It Relates to WCAG
PDF reading order is the document analogue of WCAG 1.3.2 Meaningful Sequence[2]: the programmatically determined order must match the intended reading order. EN 301 549 clause 10.1.3.2 carries the same requirement into non-web documents by reference to the WCAG criterion[3][4]. For a PDF, "programmatically determined" means the tag tree, not the content stream. ISO 14289-1 (PDF/UA-1) makes the same split explicit: the structure tree is the authoritative source of order for conforming readers[1].
Practical Implications
- Author the order in the source application before exporting. In InDesign, set the sequence in the Articles panel and check "Use for Reading Order in Tagged PDF" on export. In Word, use built-in heading styles and a linear body flow; text boxes, floating images with "In front of text" wrapping, and manually positioned frames drop out of the natural flow and land in unpredictable spots in the tag tree.
- Verify in Acrobat Pro via the Reading Order tool (Accessibility tools > Reading Order) and the Tags panel. The Reading Order tool shows numbered regions; the Tags panel shows the depth-first walk the assistive technology will use.
- Test end-to-end with a screen reader (NVDA on Windows, VoiceOver on macOS) by playing the document top to bottom. Visual inspection misses tag-tree errors because the eye re-sequences the page without help.
- Mark decorative elements (rules, watermarks, repeated page headers and footers, background graphics) as artifacts so they are skipped by the tag-tree walk entirely.
- Columns, sidebars, pull quotes, and figure captions need explicit sequencing decisions -- there is no default that handles all four correctly.