Logical reading order in PDFs: what 'Needs manual check' means and how to pass it

Logical reading order is the order in which a screen reader announces the content of a PDF. In a tagged PDF, that order comes from the tags, the hidden structure that tells assistive technology what each part of the page is and what comes next. Acrobat's Accessibility Checker cannot judge whether that order makes sense, so it reports Logical Reading Order as "Needs manual check" on every document it checks. Under WCAG 2.1, the order is right when it keeps the author's meaning, and judging meaning takes a person. This guide explains what the flag means, the three different orders inside a PDF, a 15-minute check you can do with free tools, and how to fix what you find in Acrobat or, more cheaply, in the source file.

What "Logical Reading Order: Needs manual check" means in Acrobat

Acrobat's checker gives each rule one of four statuses: Passed, Failed, Skipped By User or Needs Manual Check. Adobe defines the last one as an item the checker could not test automatically, which you verify yourself. For Logical Reading Order, Adobe's help page tells you to confirm that the order shown in the Tags panel matches the logical order of the document. UCLA's Disabilities and Computing Program explains why the item is always marked this way: no program can decide whether a reading order is reasonable.

So the flag is not a finding. It appears on well-made and broken documents alike, and tells you only that nobody has checked yet.

A wrong order hurts screen reader users most. It also affects people who read in Reflow view or with magnification, one column at a time, and keyboard users moving through links and form fields.

Picture a public hearing notice with the date, time and place in a shaded box at the top right. If that box is tagged last, a screen reader user hears the legal description and the clerk's signature before learning when the hearing is. Every word is there, and the meaning is still damaged.

What WCAG 2.1 success criterion 1.3.2 requires

Success criterion 1.3.2 Meaningful Sequence (Level A) reads:

"When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined."

In a PDF, "programmatically determined" means the order is written into the tags, where assistive technology can read it. The W3C's Understanding document adds that more than one order can be correct, and only one has to be provided. That is why the check takes judgment. A sidebar can come before or after the story beside it. A caption read in the middle of a sentence cannot.

Criterion 1.3.2 works alongside 1.3.1 Info and Relationships, which asks that structure shown visually, such as headings, lists and tables, also exists in the tags. Criterion 1.3.1 says what each piece is. Criterion 1.3.2 says the pieces arrive in an order that keeps their meaning. The W3C's PDF technique PDF3 covers both reading order and tab order, and its test is simple: listen with a screen reader, press Tab through the document, and confirm everything arrives in the right order.

Tag order, content order and tab order in a PDF

A PDF can carry three different orders, and they do not always agree. Most confusion about reading order comes from fixing one and checking another.

Clemson University's accessibility guide calls tag order the most critical, because a screen reader follows the tag tree from top to bottom. Tab order is the easiest to settle: Acrobat's checker can fix it, or choose Use Document Structure in each page's properties, and focus then follows the tags.

Acrobat's Reading Order tool has its own Order panel, which numbers regions of the page. It is useful for seeing the layout, but it is not the final word: Clemson's guide describes the Order panel as showing the original content order rather than the tag order. Whatever you change, confirm the result in the Tags panel, which is where Acrobat's own checker tells you to look.

How to check reading order in a PDF in 15 minutes

You do not need to listen to all 200 pages of a budget book. Check the pages most likely to go wrong: the first page, a page with columns or a sidebar, a page with a table or chart, and any page with form fields.

1. Confirm the file is tagged. Run Acrobat's Accessibility Checker. If the Tagged PDF rule fails, there is no reading order to check yet, so the document needs tags first.
2. Walk the Tags panel. Open it from View, Show/Hide, Side panels, Accessibility tags. Choose Highlight Content from the panel's options menu, expand the tags and step through them. The highlight should move across the page the way a reader's eyes would.
3. Look at Reflow view. Choose View, Zoom, Reflow. Acrobat shows the page as a single column, and Adobe suggests Reflow as a quick check of reading order. Lines from two columns should not alternate, and running headers, footers and page numbers should not appear, because Acrobat leaves artifacts out of Reflow.
4. Listen with a free screen reader. NVDA (opens an external site) from NV Access is free for Windows. Open the PDF in Acrobat Reader, press Insert+Down Arrow to read from the cursor, Control to stop and H to jump between headings. If you would rather not install a screen reader, the free PAC checker (opens an external site) has a screen reader preview that shows what will be read, and in what order.
5. Tab through the page. Press Tab repeatedly. Links and form fields should receive focus in the same order you read them.
6. Write down what you decided. Note the pages you checked and the result. A dated note is evidence if anyone asks later.

What a correct reading order looks like

Correct means the meaning survives. These are the checks that catch most problems.

Artifacts are page content marked as decoration, so screen readers skip it. Adobe recommends marking page numbers, headers and footers this way, and the same goes for decorative lines and borders.

Multi-column newsletters, annual reports with callout boxes, footnoted budget narratives and bilingual notices raise harder questions, such as whether a sidebar belongs before or after the story and where a footnote should be read. Our guide to reading order in complex PDF layouts takes them pattern by pattern.

How to fix reading order in Acrobat

Acrobat Pro gives you three tools. Use the most precise one you are comfortable with, and keep a copy of the original.

• The Tags panel. Drag a tag to where it belongs, and a line shows where it will land. To hide a running header or page number, right-click its tag and choose Change Tag to Artifact. This is the most precise method and the slowest.
• The Reading Order tool. Find it under All tools, Prepare for accessibility. It draws numbered boxes over the page, and you can drag a box to a new position, change a region's tag, or mark it Background/Artifact.
• The Content panel. It lists the page's objects in content order. Adobe suggests it for reflow problems the Reading Order tool cannot fix, and warns that editing content objects can damage a PDF. Treat it as a last resort.

The Reading Order tool is quick and carries risk. Adobe says it is meant for PDFs tagged in Acrobat, not files tagged on export from Word or InDesign. Undo does not work for every operation, so save a copy first. Clear Page Structure removes the tags from every page visible on screen, even partly, and tags drawn by hand carry less detail, such as lists, than automatic tagging. After any change, check the Tags panel again, then listen.

Fix the reading order at the source in Word and InDesign

Every fix made in Acrobat disappears the next time someone exports the file. A monthly newsletter or recurring agenda packet is cheaper to fix once, in its template.

• Word. Use the built-in heading styles and Word's own list and table tools. Keep sidebars and callouts in the main flow of the text at the point they should be read, not in floating text boxes, which are anchored to a paragraph that may be far from where they appear. Microsoft notes that images not set In Line with Text may be inaccessible to screen readers. When you save as PDF, keep the option Document structure tags for accessibility selected.
• InDesign. Open the Articles panel (Window, Articles), add the page items in the order they should be read, and choose Use for Tagging Order in Tagged PDF from the panel menu. When you export with Create Tagged PDF turned on, InDesign applies that order.

How Ockem Proof handles reading order

Ockem Proof, our product, divides the work: software repairs and flags, and a person makes the final call.

• Repair. On an untagged document, Proof builds the structure automatically. On a document with broken structure, it rebuilds in place and keeps what is already correct, such as figures, tables, links and lists. Any automated change that does not measurably improve the document is discarded, never saved.
• Detect. Proof compares the visual order of each page with its tag order. Content with no tags at all is a confirmed failure. Pages where the two orders disagree are flagged for review, and a document whose only open items are reviews shows Needs review, never Failed.
• Review. Each flagged page opens with a numbered overlay showing the exact order assistive technology will follow, block by block. If it is wrong, you draw the correct order directly on the page, and screen reader users are pointed to a keyboard method. The review shows flagged pages only.
• Record. Your reviewer confirms each flagged page, and the verification is recorded on the document's certificate as your organization's attestation. Proof certifies reading order only on evidence its audit actually had.
• Stop honestly. A document exported with no repairable structure is flagged for re-authoring, with the reason stated.

In Ockem's measurements of production documents in August 2026, the median document needs one manual check, and the 90th percentile needs two. The manual check we most often see left over is logical reading order.

Final reading order stays a person's decision because WCAG makes it a judgment call: more than one order can be correct, and choosing takes someone who knows what the document is for. Acrobat's checker lists reading order as a manual check on every document. Proof repairs the structure first and puts a numbered order in front of your reviewer on the pages it flags. This comparison was written by Ockem. The reading order rule has the details.

See it on your own files

You can try one PDF (opens an external site) of up to 10 pages free, with no account. To count your PDFs first, use the free PDF inventory tool. For how Proof handles this check, see the reading order rule. Related guides: reading order in complex layouts, which checks software can fix and free PDF accessibility checkers compared.

Questions

This guide explains the rules in plain language. It isn’t legal advice. Check how they apply to your organization with counsel.