Step-by-Step: Setting Logical Reading Order in Scanned PDFs

Step-by-Step: Setting Logical Reading Order in Scanned PDFs is one of the most overlooked yet critical tasks in PDF accessibility remediation. When a scanned document is converted to PDF, screen readers often process content in a fragmented, illogical sequence — jumping between headings, sidebars, and body text without structure. This breaks comprehension for users relying on assistive technology and puts organizations at risk of WCAG 2.2 non-compliance and ADA-related lawsuits. Establishing a correct tag tree hierarchy ensures content flows the way sighted users visually scan a page: title, headings, paragraphs, then supplementary elements. This guide walks through practical techniques for fixing reading order in Adobe Acrobat, verifying structure with accessibility checkers, and testing real-world screen reader navigation outcomes — so your scanned PDFs become genuinely usable, not just technically tagged.

Quick Answer

To set a logical reading order in a scanned PDF, first perform OCR to convert the scanned image into searchable text. Then add accessibility tags, verify the document structure, adjust the Reading Order panel so content flows naturally from top to bottom and left to right, test with a screen reader, and validate the document using an accessibility checker.

Definition Box

What Is Logical Reading Order?

Logical Reading Order is the sequence in which assistive technologies, including screen readers, present document content to users. It should accurately reflect how a sighted reader naturally reads the page, ensuring headings, paragraphs, tables, images, and lists are announced in the correct order.

Why Does Reading Order Matter in Scanned PDFs?

A visually correct PDF can still be inaccessible if the reading order is incorrect. Screen readers rely on document tags—not visual layout—to determine how content should be presented.

When reading order is incorrect:

• Headings may be announced after body text.
• Columns may be read in the wrong sequence.
• Tables become confusing.
• Lists lose their structure.
• Images may interrupt paragraphs unexpectedly.
• Users navigating with assistive technology experience unnecessary barriers.

Proper reading order is required for accessibility standards such as:

• WCAG 2.2
• PDF/UA (ISO 14289)
• Section 508
• Americans with Disabilities Act (ADA)

What Tools Can You Use to Set Reading Order?

Several accessibility tools allow you to inspect and modify reading order.

Tool	OCR	Reading Order Editing	Accessibility Checker	Best For
Adobe Acrobat Pro	✔	✔	✔	Professional PDF remediation
CommonLook PDF	✔	✔	✔	Enterprise accessibility
axesPDF for Word	Partial	Limited	✔	Accessible document creation
PAC (PDF Accessibility Checker)	✖	✖	✔	PDF/UA validation
Foxit PDF Editor	✔	Limited	Limited	Basic accessibility editing

How to Set Logical Reading Order in a Scanned PDF

Step 1: Determine Whether the PDF Is Scanned

Open the document and try selecting text.

If you cannot highlight or copy text, the document is likely image-only and requires OCR before accessibility remediation can begin.

Step 2: Run Optical Character Recognition (OCR)

OCR converts scanned images into machine-readable text.

In Adobe Acrobat Pro:

1. Open the PDF.
2. Select Scan & OCR.
3. Click Recognize Text.
4. Choose the document language.
5. Start OCR processing.
6. Save the document.

Review the OCR output carefully, as recognition errors can affect accessibility.

Step 3: Add Accessibility Tags

Tags provide the structural information that screen readers depend on.

To generate tags in Acrobat:

• Open Accessibility Tools.
• Select Autotag Document.
• Allow Acrobat to generate an initial tag structure.

Automatically generated tags should always be reviewed and corrected manually.

Step 4: Open the Reading Order Tool

Navigate to:

Tools → Accessibility → Reading Order

Acrobat overlays numbered regions on each page.

Each number represents the order in which assistive technology will read that content.

Step 5: Review the Existing Reading Order

Inspect every page carefully.

Check whether:

• Titles appear first.
• Headings precede paragraphs.
• Multi-column layouts read correctly.
• Sidebars are positioned appropriately.
• Footnotes appear after main content.
• Captions remain attached to images.

Reading order should match the intended reading experience rather than the visual placement alone.

Step 6: Reorder Content

If elements appear out of sequence:

1. Select the affected content.
2. Assign the correct content type.
3. Drag or reposition reading order regions where supported.
4. Verify numbering updates correctly.

Pay close attention to:

• Headings
• Lists
• Tables
• Images
• Decorative graphics
• Captions

Step 7: Verify the Tag Tree

The Reading Order panel and the Tags panel work together.

Open:

View → Show/Hide → Navigation Panes → Tags

Confirm that:

• Headings use H1–H6 correctly.
• Paragraphs are tagged as <P>.
• Lists contain <L>, <LI>, <Lbl>, and <LBody> elements.
• Tables include proper table structure.
• Figures contain alternate text where appropriate.

The tag tree ultimately determines how assistive technologies interpret the document.

Step 8: Check Multi-Column Layouts

Multi-column documents frequently contain reading order issues.

Instead of reading:

Left column → Right column

A screen reader might read:

Top left → Top right → Middle left → Middle right

Correct the sequence so users receive information logically.

Step 9: Test with a Screen Reader

Never rely solely on visual inspection.

Test using:

• NVDA
• JAWS
• VoiceOver
• Narrator

Navigate by:

• Heading
• Paragraph
• Table
• List
• Landmark

The reading experience should feel natural and predictable.

Step 10: Run an Accessibility Checker

Perform a final validation.

Recommended tools include:

• Adobe Accessibility Checker
• PAC (PDF Accessibility Checker)
• CommonLook Validator

Look for issues involving:

• Missing tags
• Incorrect reading order
• Untagged annotations
• Missing alternative text
• Table structure errors

Common Reading Order Problems

Accessibility professionals frequently encounter these issues:

• OCR text split into multiple blocks
• Images interrupting paragraphs
• Incorrect heading hierarchy
• Decorative graphics announced unnecessarily
• Sidebars inserted into main content
• Table cells read incorrectly
• Floating text boxes read out of order
• Footnotes appearing before body text

Correcting these issues significantly improves the user experience.

Best Practices for Accessible Reading Order

Follow these recommendations during remediation:

• Perform OCR before tagging.
• Review every page manually.
• Verify automatic tags.
• Maintain a logical heading hierarchy.
• Keep captions associated with images.
• Tag decorative images as artifacts.
• Preserve table relationships.
• Test with multiple screen readers.
• Validate against PDF/UA standards.

Reading Order Checklist

Task	Completed
OCR applied	☐
Text verified	☐
Tags generated	☐
Reading order reviewed	☐
Heading structure validated	☐
Tables tagged correctly	☐
Images have alt text	☐
Decorative items artifacted	☐
Screen reader tested	☐
Accessibility checker passed	☐

How Reading Order Supports WCAG and PDF/UA Compliance

Logical reading order directly supports several accessibility requirements.

Relevant success criteria include:

• WCAG 1.3.1 – Info and Relationships
• WCAG 1.3.2 – Meaningful Sequence
• WCAG 2.4.6 – Headings and Labels
• PDF/UA ISO 14289 Requirements

Meeting these standards improves accessibility for users of screen readers, refreshable Braille displays, speech recognition software, and other assistive technologies

Expert Tips for Better PDF Remediation

Experienced accessibility specialists rarely rely on automated remediation alone.

Instead, they:

• Review OCR accuracy line by line.
• Inspect the tag tree after every major edit.
• Compare reading order with the document’s visual flow.
• Test keyboard navigation where interactive elements exist.
• Validate the final PDF using independent accessibility checking tools.

This workflow reduces compliance issues and creates a more consistent experience across assistive technologies.

External Resources

For official guidance, consult:

• Adobe Acrobat Accessibility Documentation
  https://helpx.adobe.com/acrobat.html
• W3C Web Accessibility Initiative (WAI)
  https://www.w3.org/WAI/

[SOURCE NEEDED]: If referencing accessibility adoption rates, PDF usage statistics, or remediation performance metrics, cite current research from Adobe, W3C, ISO, or government accessibility publications rather than estimating figures.

Frequently Asked Questions