PDF Accessibility: Making Documents Readable for Everyone
A PDF that's beautiful on a phone or computer screen can be unusable for someone using a screen reader. With ~15% of the global population having some form of disability, accessible PDFs aren't a nice-to-have — they're a baseline requirement for any document distributed to a general audience.
The basics: tagged PDFs
An accessible PDF has a 'tag tree' — a parallel structure that tells assistive technology what each piece of content is. Headings are tagged as headings, lists as lists, tables as tables. Without tags, a screen reader sees one continuous stream of text with no structural cues.
Source-first accessibility
Accessibility is far easier to build in than to add later. Use proper heading styles in Word, real bulleted lists not manual asterisks, real tables not text formatted to look like tables. Add alt text to every image. When you export to PDF, all of this structure carries through automatically.
Reading order matters
PDFs have a reading order that determines what a screen reader announces first, second, third. By default this follows the document's content order, but complex multi-column layouts can confuse this. Test your exported PDFs by listening to them with a screen reader — VoiceOver on Mac, NVDA on Windows (free) — to verify the order makes sense.
Common accessibility failures
Scanned PDFs without OCR'd text layers — invisible to screen readers. Images without alt text — silent. Tables built as text with manual spacing — read column-by-column instead of row-by-row. Form fields without labels — confusing. PDFPuddle's OCR PDF tool helps with the first; the rest require source-document attention.
Standards
WCAG 2.1 (Web Content Accessibility Guidelines) covers PDFs. PDF/UA (ISO 14289) is the dedicated PDF accessibility standard. For US federal contracting, Section 508 compliance is mandated. Tools like Adobe Acrobat Pro's Accessibility Checker validate against these standards.