Skip to main content
WCAG coverage · Perceivable

Reading order & document structure

WCAG 1.3.1 · 1.3.2 Meaningful Sequence · AAUTOMATICDECISION QUEUEATTESTATION

What the rule requires

A PDF carries a hidden structural outline that tells assistive technology what to read and in what order. When it’s missing or scrambled, a screen reader delivers the page as gibberish — headlines after footnotes, captions mid-sentence.

How Proof clears it

  1. Builds structure automatically on untagged documents, and rebuilds broken structure in place — preserving what’s already correct (figures, tables, links, lists).

  2. Self-validates: any automated change that doesn’t measurably improve the document is discarded, never saved.

  3. Per-page visual review: a numbered overlay shows the exact order assistive tech will follow; your reviewer confirms each flagged page, and the verification is recorded on the compliance certificate.

What to expect

Final reading order is confirmed by a person — WCAG makes it a judgment call, and any tool claiming to fully automate it is overclaiming. The rare document whose content was exported with no repairable structure gets flagged honestly for re-authoring, with the reason stated.

Reading order
page 4 of 9
NUMBERED IN THE ORDER ASSISTIVE TECH WILL READ
Mark page reviewed
4 of 9 reviewed
verification recorded on the certificate, by name

Related rules

Run the full profile on one of yours.