Guide
How to fix PDF reading order
A working method for finding and repairing reading order, free in Acrobat and faster in Taggart, including the two-column case that costs the most time.
About 15 minutes · involved
Find it before you fix it
You cannot judge reading order by looking at the page. You have to look at the tree.
In Acrobat Pro: View → Show/Hide → Navigation Panes → Tags, then Options → Highlight Content. Now selecting a tag outlines the region it covers. Walk down the tree with the arrow keys and watch where the highlight goes. The first time it jumps somewhere unexpected, you have found your first defect.
In Taggart: the reading-order editor draws numbered badges on the rendered page, taken from the real structure tree. The order is visible at a glance rather than something you reconstruct by walking a tree. The check engine also reports the specific transpositions before you open the editor:
On page 4 the structure tree order disagrees with the visual reading order for 61 of 210 element pairs (29%), in a 2-column layout.
The two-column case
This is where the time goes, and it is worth understanding why.
Auto-tagging tools order elements by sweeping the page top to bottom, left to right. On one column that is correct. On two it interleaves them — left line 1, right line 1, left line 2, right line 2 — so the document reads as two shuffled halves.
Fixing it in Acrobat means dragging roughly half the elements individually, with no multi-select and no reliable batch undo. On a 20-page paper that is a solid afternoon.
Fixing it in Taggart means selecting a run and moving it with Alt and the arrow keys, with an undo stack that spans the batch.
If the document is right-to-left, the correct order is right column first. Auto-taggers sweep left to right regardless of script, so Hebrew and Arabic two-column layouts are always wrong in the same way. The condition →
Step by step, free, in Acrobat Pro
View → Show/Hide → Navigation Panes → Tags.Options → Highlight Content.- Click the first tag. Confirm the highlight is on the content that should be read first.
- Arrow down through the tree, watching each highlight.
- When one lands in the wrong place, drag the tag to its correct position. The insertion line shows where it will land.
- Save a copy before you start. Acrobat’s undo across a run of tag moves is not dependable.
- Re-check with
Accessibility → Accessibility Check, and then by actually reading the document with a screen reader.
Step by step, in Taggart
- Drop the PDF in. The check runs in about a second and reports the disagreements per page.
- Open Reading order. Numbered badges appear on the page; the tree is beside it.
- Click a badge to select its element, or click a tree item to highlight it on the page — the selection is linked both ways.
- Alt + ↑ / ↓ moves the selected element. Cmd/Ctrl + Z undoes across the batch.
- Open Screen reader to hear the resulting sequence before you export.
- Export. The output is re-rendered against the original and compared at SSIM ≥ 0.999 before you get it.
The thing to do first
If the source document still exists, fix the source and re-export. A correctly structured Word or InDesign file exports with a correct reading order, and that costs nothing. In InDesign specifically, the Articles panel with Use for Tagging Order ticked is a two-minute job that eliminates this entire task.
Frequently asked questions
Order panel or Tags panel?
Tags panel, always. The Order panel shows a separate per-page ordering that Acrobat keeps for its own tooling; editing it does not reliably update the structure tree, which is what a screen reader follows. Working in the Order panel is the single most common way to spend an afternoon and change nothing.
How do I know what the correct order is?
Read the page aloud in the order you would naturally read it. That is the answer. Where it is genuinely ambiguous — a sidebar, a pull quote — the question is where it belongs in the argument, and there is usually a right answer once you ask it that way.
Does reordering change the page?
No. Reading order lives in the structure tree, a separate object graph from the content streams that paint the page. Taggart proves it on every export by re-rendering both files and comparing them.
Related failure conditions
- 09-001 Tags are not in logical reading order The order of elements in the structure tree does not match the order a human would read the page. This is the single most common substantive defect in tagged PDFs and the one Acrobat's own tooling handles worst.
- 28-001 An annotation is not in correct reading order The annotation's position in the structure tree does not match where it appears on the page.
- TG-RTL-004 Reading order is not right-to-left aware Auto-tagging tools order blocks left-to-right, top-to-bottom. In a Hebrew two-column layout the correct order is right column first.
Check your own file. Taggart's validator is free and unlimited — no page cap, no watermark, no account.
Last updated .