How to Check Reading Order and Accessibility After PDF Conversion

Problem

A converted document can look perfect while a screen reader announces the footer before the body, loses table relationships, or exposes only a meaningless image filename. For keyboard and assistive-technology users, structural defects are content defects.

Who should use this

Useful for teams publishing course material, public forms, reports, policies, company procedures, and shared PDF or Word documents.

Formula and concept

Define the delivery format and audience first. PDF, Word, and images expose different accessibility capabilities; if images are the only output, provide readable text or a fallback instead of relying on zoom.

Treat heading levels as navigation, not font size. Check H1, H2, and H3 logic after conversion so large decorative text is not mistaken for a heading and important sections do not become plain paragraphs.

Two-column and sidebar layouts are high-risk reading-order areas. Move through the document with the keyboard or read-aloud tool to ensure the left column is completed before the right, rather than interleaving lines.

Check table headers and the relationship between rows and data. A visual grid may not expose structure; repeated pages still need understandable headers, and complex tables may need to be simplified into smaller blocks.

Images, charts, and scanned stamps need a useful text alternative or surrounding explanation. Describe information a reader needs; do not expose “image123” or a filename as the description.

Check form labels, order, required hints, and error messages. A focusable field is not enough; its name and instructions should appear next to it in the reading sequence.

Start keyboard testing at the first interactive element instead of substituting a mouse. Confirm visible focus, sensible order, and no traps in embeds or hidden controls; reproduce once in another browser.

Use the W3C WCAG 2.2 guidance on non-text content and link purpose to describe defects in testable terms. Attach a page, element, and fix for every issue (https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html).

Before handoff, have someone outside production follow the keyboard and read-aloud path. A fresh reviewer catches order errors the author has learned to ignore and can leave evidence in the version record.

Step by step

1. Confirm the final format, audience, and need for a readable fallback.
2. Check heading levels and two-column or sidebar reading order.
3. Validate headers, row relationships, and page breaks for every table.
4. Add meaningful text alternatives for images, charts, and stamps.
5. Test focus, form labels, and error hints with the keyboard.
6. Reproduce high-risk pages with read-aloud tools and log page and element.
7. Have a second reviewer confirm the fixed version and preserve the record.

Worked example

A two-column research report looked unchanged in Word, but read-aloud interleaved the columns line by line. The team changed them to sequential blocks, reset headings, and added a chart summary; a second reviewer completed the document by keyboard before PDF delivery.

Common mistakes

• Accepting with only a mouse and visual preview.
• Treating font size as heading structure.
• Ignoring columns, sidebars, and tables across pages.
• Using a filename instead of alternative text.
• Making fields focusable without labels or error hints.
• Skipping a second reviewer after fixes.

Related guides

Related workflows