PDF Accessibility: Making Documents Readable for Everyone
Most PDFs are nightmares for screen readers. Here's how to fix that and why it actually matters.
Let's be honest: most PDFs are terrible for anyone using assistive technology. You know why? Because whoever created them assumed everyone experiences documents the same way. They don't.
About 15% of the global population lives with some form of disability. That's over a billion people. And when you share a PDF that isn't accessible, you're basically telling a significant chunk of your audience "this information isn't for you." Whether you're sharing a menu, an invoice, a form, or a report, that's not great.
What Actually Makes a PDF Accessible?
An accessible PDF works with screen readers, keyboard navigation, and other assistive technologies. But what does that mean practically?
Proper document structure. Just like HTML has headings, paragraphs, and lists, PDFs need the same semantic tagging. A screen reader needs to know what's a title, what's a paragraph, what's a caption. Without that structure, it's just visual chaos read in random order.
Alt text for images. Every meaningful image needs a text description. Decorative images should be marked as artifacts so screen readers skip them. This seems obvious but you'd be shocked how many corporate annual reports completely ignore this.
Logical reading order. Your PDF might look fine visually, but a screen reader reads in document order, not visual order. That fancy two-column layout? Could be completely nonsensical when read aloud.
Color contrast. Text needs sufficient contrast against backgrounds. WCAG requires a 4.5:1 ratio for normal text, 3:1 for large text. Light gray text on white backgrounds fails this (and honestly, why do designers keep doing that?).
No color-only information. If your chart says "red bars show losses," someone with color blindness is out of luck. Use patterns, labels, or icons in addition to color.
The PDF Formats That Matter
There's PDF, and then there's PDF/UA (Universal Accessibility). PDF/UA is the ISO standard specifically for accessible PDFs. It enforces all those structural requirements I mentioned.
When you export a PDF, most software gives you a checkbox for "tagged PDF" or "accessibility features." That's a start, but it doesn't guarantee PDF/UA compliance. You need to actually structure your source document properly first.
Starting From Scratch: Creating Accessible PDFs
The easiest time to make a PDF accessible is before it becomes a PDF. Here's how to set yourself up for success:
Use styles in Word or Google Docs. Don't just make text bigger and bold it — use Heading 1, Heading 2, Normal paragraph styles. This creates semantic structure that carries over to the PDF.
Add alt text to images in your source document. Right-click images in Word or Google Docs and add a description. This exports with the PDF.
Use built-in list formatting. Don't just type "- Item 1" manually. Use the actual bullet list or numbered list buttons. Screen readers announce lists differently than plain text.
Create simple tables. Avoid merged cells, nested tables, or tables used for layout. Add header rows and column headers. Complex tables are accessibility nightmares.
When you export to PDF from Word or Google Docs, check the "tagged PDF" option. That's your baseline. Modern versions of Word and Google Docs do a decent job if your source document is structured well.
Fixing Existing PDFs (Remediation)
So you've got a PDF that's already out in the wild, and it's not accessible. Can you fix it?
Maybe. It depends how it was created.
Digitally created PDFs (from Word, InDesign, etc.) can often be remediated. Adobe Acrobat Pro has an Accessibility Checker and tools to add tags, alt text, and reading order. It's manual work, but doable.
Scanned PDFs are basically images. You need to run OCR (Optical Character Recognition) first to make the text selectable, then add tagging. If you need to convert scanned documents to searchable PDFs, that's step one before accessibility work.
Adobe Acrobat Pro is the industry standard for remediation, but it's expensive ($240/year as of 2026). Free tools like PAC (PDF Accessibility Checker) can validate but not fix issues.
The WCAG Connection
You've probably heard of WCAG (Web Content Accessibility Guidelines). They're the international standard for digital accessibility, and yes, they apply to PDFs too.
WCAG has three levels: A (minimum), AA (mid-range), and AAA (gold standard). Most legal requirements target Level AA. For PDFs, that means:
- Proper structure and tagging
- Alt text for informative images
- Sufficient color contrast (4.5:1 for text)
- Keyboard accessibility for forms and links
- No flashing content (seriously, don't do this)
- Clear language and readable fonts
If you're creating PDFs for government agencies, educational institutions, or large corporations, WCAG AA compliance isn't optional. The ADA (Americans with Disabilities Act), Section 508, and similar laws worldwide require it.
Accessible PDF Forms
Forms are where accessibility gets tricky. You need proper field labels, tab order, and instructions that screen readers can announce. Here's what matters:
Every field needs a label. "First Name:" should be associated with the input field, not just visually near it. Screen readers need that explicit connection.
Logical tab order. When someone hits Tab, fields should activate in a sensible order, not jump around randomly. Adobe Acrobat lets you set this manually.
Clear instructions. If a field requires a specific format (like MM/DD/YYYY for dates), that instruction needs to be part of the field's accessible description, not just nearby text.
If you're merging multiple forms into one document, make sure the combined result maintains field labels and tab order across all pages.
Testing Your PDF
How do you know if your PDF is actually accessible? You test it.
Use Adobe Acrobat's Accessibility Checker. It's not perfect, but it catches obvious issues like missing alt text, contrast problems, and structural errors.
Try a screen reader. NVDA (Windows, free) or VoiceOver (Mac, built-in) will show you what blind users experience. Open your PDF and listen. Does it make sense? Can you navigate headings? Are images described?
Keyboard-only navigation. Unplug your mouse. Can you fill out forms, follow links, and navigate the document using only Tab, Enter, and arrow keys? If not, it's not accessible.
PAC (PDF Accessibility Checker). Free tool from the PDF/UA Foundation. It validates PDF/UA compliance and generates detailed reports. More technical than Acrobat's checker but more thorough.
Common Mistakes to Avoid
Here's what trips people up:
Image-based PDFs. Scanning a document and calling it a PDF doesn't make it accessible. It's just a picture. Always use OCR to make scanned documents searchable first.
Empty alt text. Leaving alt text blank is not the same as marking an image decorative. Screen readers may announce "image" with no context. Either write meaningful alt text or properly mark decorative images as artifacts.
Using spaces for layout. Don't hit spacebar 50 times to indent something. Use proper indentation formatting. Screen readers will read each space, and it's chaos.
Relying on color alone. "Click the green button" doesn't help someone with color blindness. Use text labels, not just colors.
Weird reading order. Visual design doesn't always match document order. Sidebars, callout boxes, and multi-column layouts can confuse screen readers. Always check reading order manually.
Why Bother?
Look, I know this seems like extra work. And it is, if your workflow wasn't designed with accessibility in mind.
But here's the thing: accessible documents are better for everyone. Clear headings help everyone scan content faster. Alt text helps when images don't load. Proper structure makes your content work on phones, tablets, and future devices we haven't even invented yet.
Plus, it's the right thing to do. Information shouldn't be locked away from people just because they interact with technology differently than you do.
And if that's not motivating enough, legal compliance is a real thing. Accessibility lawsuits are increasing. Government agencies require it. Educational institutions must meet it for accreditation. This isn't optional anymore.
Start small. Make your next PDF accessible. Learn the tools. Build it into your workflow. Future you (and everyone using assistive tech) will thank you.