PDF Accessibility: The Complete Compliance Guide for 2026
I received a complaint from a visually impaired customer who could not read our product catalog. The PDF looked beautiful on screen but was completely inaccessible to screen readers. Every image had no alt text, the reading order was wrong, and the headings were just big bold text — not actual heading tags. Fixing it took a week. Building it right from the start would have taken an hour.
What Makes a PDF Accessible
An accessible PDF has a hidden structure layer (called "tags") that tells assistive technology what each element is: this is a heading, this is a paragraph, this is a table with 3 columns, this image shows a product photo. Without tags, a screen reader sees a flat stream of text with no structure.
The Accessibility Checklist
The PDF Accessibility Checker tests against these criteria:
- Document title set — The title appears in the browser tab and screen reader announcements
- Language specified — Screen readers need to know the language to pronounce words correctly
- Headings tagged properly — H1, H2, H3 in logical order, not just styled text
- Images have alt text — Every meaningful image needs a description
- Tables have headers — Row and column headers must be marked
- Reading order is logical — Content reads in the correct sequence
- Links are descriptive — "Download the report" not "click here"
- Color is not the only indicator — Do not rely solely on color to convey information
- Sufficient color contrast — 4.5:1 ratio for normal text, 3:1 for large text
- Form fields have labels — Every input field needs an associated label
Legal Requirements
| Standard | Applies To | Key Requirements |
|---|---|---|
| Section 508 (US) | Federal agencies | All electronic documents must be accessible |
| ADA (US) | Public accommodations | Websites and documents must be accessible |
| EN 301 549 (EU) | Public sector | WCAG 2.1 AA compliance required |
| AODA (Canada/Ontario) | Organizations 50+ employees | Accessible documents required |
| PDF/UA (ISO 14289) | Universal | Technical standard for accessible PDFs |
According to W3C WCAG techniques for PDF, accessible PDFs must meet the same success criteria as web content.
Common Accessibility Failures
- Scanned documents without OCR. A scanned PDF is an image. Screen readers cannot read images. Run OCR first.
- Decorative images without empty alt text. Decorative images should have alt="" to tell screen readers to skip them.
- Tables used for layout. If a table is used for visual layout (not data), it confuses screen readers.
- Missing document structure. No headings, no lists, no tagged paragraphs — just a wall of text.
- Incorrect reading order. Multi-column layouts where the reading order jumps between columns incorrectly.
How to Fix an Inaccessible PDF
- Run the Accessibility Checker to identify issues
- Add missing alt text to images
- Tag headings, lists, and tables properly
- Set the document language and title
- Fix the reading order
- Re-check until all issues are resolved
Building Accessible PDFs from the Start
It is much easier to create an accessible PDF than to fix one after the fact:
- Use heading styles (not just bold text) in your source document
- Add alt text to images in Word/InDesign before converting to PDF
- Use actual tables for tabular data, not tabs or spaces
- Use the PDF Editor for final accessibility adjustments
Related Tools
As Adobe accessibility guidelines emphasize, accessibility is not an afterthought — it should be part of the document creation process from the beginning.
Check your PDF accessibility now.
Run the Accessibility Checker →