PDF Accessibility Checklist for Tagged, Screen-Reader-Friendly PDFs

Q: What is a tagged PDF, and why does it matter?

A tagged PDF contains a hidden structure tree that labels headings, paragraphs, lists, tables, and images. Screen readers use these tags to navigate the document; without them, the reader gets a flat wall of text in a random order.

Q: Can a scanned PDF be made accessible?

Yes, but it takes two extra steps: run OCR to create a real text layer, then tag the result. Without OCR there is no text for the screen reader to read at all, so tagging alone is not enough.

Q: How do I test whether my PDF is actually accessible?

Run your tool's built-in accessibility checker first, then test with a real screen reader (NVDA is free on Windows, VoiceOver is built into Mac and iPhone). Automated checks catch structure errors; only a screen reader shows you what the experience feels like.

October 24, 2026 · 5 min read · By the DollarWise team

PDF Accessibility Checklist for Tagged, Screen-Reader-Friendly PDFs

On this page

An untagged PDF is a locked door for anyone using a screen reader: the text exists, but there is no map of what is a heading, what is a list, or which image matters. Governments, universities, and large companies increasingly require accessible documents, and beyond compliance it is simply good practice — accessible PDFs work better for everyone, including search engines and mobile readers.

This free checklist gives you 32 concrete steps to build or repair a tagged, screen-reader-friendly PDF. It is written for document creators, office staff, freelancers, and students who need their PDFs to work for every reader. Follow the phases in order, from document setup through tables and forms to final testing. Each item is one clear action with a copy button for your own notes.

What’s inside this checklist

The checklist covers seven phases. Phase 1 sets up the document correctly: language, title, and tagged-PDF output. Phases 2 and 3 build the tag structure and fix the reading order, which is where most accessibility failures live. Phases 4 through 6 handle the details that trip people up: alt text for images, proper table structure, and form fields that screen readers can announce. Phase 7 finishes with color contrast and real-world testing, because an accessibility checker alone never tells the whole story.

The full 32-step PDF accessibility checklist

Fix the document in the source application where possible — repairing tags in a finished PDF is far slower than exporting correctly the first time.

Phase 1 — Document setup

Set the document language so screen readers use the correct pronunciation.
Give the PDF a descriptive document title that appears in the title bar.
Export or save as a tagged PDF — confirm the tags option is enabled in your tool.
Run OCR on any scanned pages so there is real text behind the images.
Confirm the file is not a flat image-only PDF before continuing.

Phase 2 — Tag structure

Verify every page has a complete tag tree with no untagged content.
Tag headings as H1 through H6 in a logical, unskipped hierarchy.
Tag body text as paragraphs (P), not as loose text runs.
Tag bulleted and numbered lists as proper list structures with list items.
Mark decorative images and design elements as artifacts so readers skip them.
Tag footnotes, captions, and quotes with their correct semantic tags.

Phase 3 — Reading order

Check the reading order on every page with multi-column or complex layouts.
Fix sidebars and callout boxes so they read in a sensible position, not mid-sentence.
Confirm headers, footers, and page numbers are artifacted or read consistently.
Verify the tab order follows the visual reading order for keyboard users.
Test the reading order with a screen reader on at least two complex pages.

Phase 4 — Images and alt text

Write concise alt text for every informative image, chart, and diagram.
Describe what the image communicates, not just what it shows.
Keep alt text under about 150 characters; put longer explanations in the body text.
Never start alt text with "image of" — screen readers already announce the element.
Provide a text alternative or data table for complex charts and infographics.

Phase 5 — Tables

Tag tables with proper table, row, and cell structure — never fake tables with tabs or spaces.
Designate header rows and columns so screen readers announce them on every cell.
Add a table summary or caption describing what the table shows.
Avoid merged cells where possible; they confuse screen reader navigation.

Phase 6 — Forms

Give every form field a clear, unique label that a screen reader can announce.
Set a logical tab order through the form fields.
Associate help text and error messages with their fields programmatically.
Mark required fields as required in the field properties, not just visually.

Phase 7 — Color, contrast, and testing

Never use color alone to convey meaning — add labels, icons, or text.
Check text contrast meets at least 4.5:1 for body text and 3:1 for large text.
Run the built-in accessibility checker and fix every reported error.

How to use this checklist

Start in your source application (Word, InDesign, Google Docs): use real heading styles, real lists, and real tables before exporting.
Export as a tagged PDF with the document language and title set, running OCR on any scanned pages first.
Work through phases 2 to 6, fixing the tag tree, reading order, alt text, tables, and form fields in that order.
Run the automated accessibility checker, fix every error, then test with an actual screen reader — NVDA is free on Windows and VoiceOver is built into Apple devices.
Save the accessible version as your master copy and re-check it after any future edits, since small changes can break tags silently.

The single biggest time-saver is step 1. A document built with proper styles in Word or InDesign exports as a nearly perfect tagged PDF in seconds; a document built with bold text pretending to be headings takes hours to repair. Accessibility starts in the source file, not in the PDF editor.

Frequently asked questions

What is a tagged PDF, and why does it matter? A tagged PDF includes a hidden structure tree that labels each element — headings, paragraphs, lists, tables, figures — the way HTML tags structure a web page. Screen readers navigate using these tags. Without them, the reader receives text in an unpredictable order with no way to jump between sections, skim headings, or understand tables.

Can a scanned PDF be made accessible? Yes, with two extra steps. First run OCR so the scanned image gains a real text layer — without it, there is nothing for a screen reader to read. Then export or repair the file as a tagged PDF and work through the checklist. OCR quality matters: proofread the recognized text, especially numbers and names, before tagging.

How do I test whether my PDF is actually accessible? Do both layers of testing. Run your PDF tool’s built-in accessibility checker to catch structural errors like missing alt text or untagged content. Then test with a real screen reader — NVDA is free on Windows, VoiceOver is built into macOS and iOS — and listen to how the document actually reads. Automated checks find the errors; only a screen reader shows you the experience.

Download the PDF Accessibility Checklist for Tagged, Screen-Reader-Friendly PDFs

#pdf #accessibility #checklist

Written by the DollarWise team

We turn confusing money topics into plain-English guides for beginners. Every article is written to be actionable on day one — no jargon, no hype, no sales pitch.