PDF Accessibility: How to Create PDFs That Everyone Can Read
An inaccessible PDF locks out users with visual impairments and fails WCAG compliance. Learn how to create tagged, readable PDFs that work with screen readers.
Over 2.2 billion people have some form of visual impairment. An inaccessible PDF locks all of them out of your content — and may violate WCAG 2.1 or Section 508 requirements if you work in government, education, or financial services. Here's how to create PDFs that everyone can actually read.
What Is PDF Accessibility?
An accessible PDF is one that works with screen readers (like JAWS, NVDA, or VoiceOver), allows keyboard navigation, and maintains logical reading order. The key mechanism is tagging — hidden metadata that tells screen readers what each element is (heading, paragraph, image, table, etc.).
The PDF/UA Standard
PDF/UA (Universal Accessibility, ISO 14289) is the international standard for accessible PDFs. A PDF/UA-compliant document must have:
- Tags for all content (no untagged elements)
- Alt text for all images, charts, and figures
- Logical reading order that matches visual order
- Properly structured headings (H1, H2, H3)
- Identified document language
- Bookmarks for documents over 9 pages
Creating Accessible PDFs From the Source
The best time to make a PDF accessible is before it becomes a PDF. In Word or Google Docs:
- Use heading styles (Heading 1, 2, 3) — not just bold text
- Add alt text to all images: right-click → Format Picture → Alt Text
- Use proper list formatting, not manual line breaks
- Give tables a header row marked as such
Checking PDF Accessibility
Adobe Acrobat's Accessibility Checker (Tools → Accessibility) is the industry standard for auditing. Free alternatives include PAC (PDF Accessibility Checker) and checking with an actual screen reader like NVDA (Windows, free) or VoiceOver (Mac/iOS, built-in).