PDF Accessibility: Making Documents Screen-Reader Friendly
Published August 27, 2026 · 8 min read
About 2.2 billion people worldwide have a vision impairment. When you create a PDF, you want everyone to be able to read it — including people who use screen readers, people who need larger text, and people who navigate by keyboard instead of a mouse. Accessible PDFs aren't just a nice-to-have; in many jurisdictions, they're a legal requirement. This guide covers everything you need to know to make your PDFs accessible.
What Makes a PDF "Accessible"?
An accessible PDF can be read, navigated, and understood by assistive technology — screen readers (JAWS, NVDA, VoiceOver), screen magnifiers, refreshable Braille displays, and keyboard-only navigation. This requires:
Tagged structure: The PDF has a logical tag tree that tells screen readers what's a heading, paragraph, list, table, image, etc.
Reading order: Content is presented in the correct order, regardless of visual layout.
Alternative text: Images have descriptive alt text that screen readers can announce.
Sufficient color contrast: Text is readable against its background (WCAG 2.1 recommends 4.5:1 for normal text, 3:1 for large text).
Language declaration: The document language is declared so screen readers use the correct pronunciation.
The PDF/UA Standard
PDF/UA (Universal Accessibility) is the ISO standard for accessible PDFs (ISO 14289-1). It defines precisely what a PDF must contain to be considered accessible. Key requirements:
All content must be tagged (no untagged content).
Tags must use standard structure types (P for paragraphs, H1-H6 for headings, Figure for images, Table for tables).
Every image must have an alt text alternative.
Content must be in logical reading order.
The document must declare its natural language.
Security settings must not prevent assistive technology access.
PDF/UA compliance is required by law in many countries for government documents, and is increasingly expected for corporate and educational documents.
Step-by-Step: How to Make a PDF Accessible
1. Start with an Accessible Source
The easiest way to create an accessible PDF is to start with an accessible source document:
Microsoft Word: Use built-in heading styles (Heading 1, Heading 2, etc.), add alt text to images, and use Word's Accessibility Checker before exporting to PDF.
Google Docs: Use heading styles and add alt text to images. Export as PDF.
LaTeX: Use the accessibility or tagpdf packages to add structure tags.
Adobe InDesign: Use the Articles panel to set reading order, add alt text to frames, and export with PDF/UA tags.
2. Tag the Document
If your PDF doesn't have tags, you need to add them. Tags tell the screen reader what each element is:
<H1> through <H6> — headings (used for navigation)
<P> — paragraphs
<L> — lists (with <LI> items and <Lbl> labels)
<Table> — tables (with <TR>, <TH>, <TD>)
<Figure> — images (with alt text in the Alt attribute)
<Link> — hyperlinks (with descriptive link text)
Tools like Adobe Acrobat Pro's "Autotag" feature can generate tags automatically, but always review the result — automated tagging is rarely perfect.
3. Fix Reading Order
Reading order determines the sequence in which a screen reader announces content. In multi-column layouts, images with captions, or complex tables, the logical reading order may not match the visual order.
In Adobe Acrobat: View → Reading Order (or the Order panel). You can drag elements to reorder them.
4. Add Alt Text to Images
Every image needs alternative text that describes what it shows. Screen readers announce this text instead of the image.
Decorative images (borders, background patterns): Mark as "artifact" — screen readers will skip them.
Informative images (charts, photos, diagrams): Write concise, descriptive alt text. "Bar chart showing Q3 revenue of $2.4M, up 18% from Q2."
Complex images (infographics, flowcharts): Provide a longer description in the document text or as a linked description.
5. Ensure Sufficient Color Contrast
Text must be readable against its background. WCAG 2.1 guidelines:
Element
Minimum Contrast Ratio
Normal text (under 18pt)
4.5:1
Large text (18pt+ or 14pt+ bold)
3:1
UI components and graphical objects
3:1
Use a contrast checker tool (WebAIM's Contrast Checker is free) to verify your colors meet these ratios.
6. Declare the Document Language
The PDF must specify its natural language so screen readers use the correct pronunciation engine. In Adobe Acrobat, go to File → Properties → Advanced and set the language. This is a metadata property, not a visual element.
Testing Accessibility
After making your PDF accessible, test it:
Adobe Acrobat Accessibility Check: Built-in automated checker that finds common issues (missing tags, missing alt text, low contrast).
Screen reader test: Open the PDF in a screen reader (NVDA on Windows, VoiceOver on Mac) and navigate through it. Does it make sense?
Keyboard navigation: Can you Tab through all interactive elements? Can you reach all content?
PDF/UA validators: Tools like PAC (PDF Accessibility Checker) by the Swiss Foundation for Accessible Reading verify PDF/UA compliance.
Common Accessibility Mistakes
Scanned PDFs without OCR: A scanned image has no text, no tags, and no accessibility. Run OCR first.
Missing headings: Using bold text instead of heading tags. Screen readers can't navigate by heading without proper tags.
Tables without header rows: Screen readers need to know which cells are headers to provide context.
Link text that says "click here": Screen reader users navigate by links. "Click here" tells them nothing. Use "Download the Q3 financial report."
Color as the only indicator: Red text for errors, green for success — these need text labels too for colorblind users.
Legal Requirements
Accessible PDFs are increasingly required by law:
ADA (Americans with Disabilities Act): US businesses must provide accessible documents.
Section 508: US federal agencies must meet PDF/UA or WCAG 2.0 standards.
EAA (European Accessibility Act): EU businesses must provide accessible digital content by 2025.
AODA (Accessibility for Ontarians with Disabilities Act): Ontario requires WCAG 2.0 compliance for large organizations.
Conclusion
Accessible PDFs serve everyone better — screen reader users, keyboard navigators, people on slow connections (tagged PDFs are often smaller), and search engines. Start with an accessible source document, tag properly, add alt text, verify reading order, and test with a screen reader. The effort is minimal; the impact is significant.
Related Guides
What Is OCR? — Make scanned PDFs text-searchable and accessible.