PDF Accessibility Checker

Check if your PDF documents meet accessibility requirements under WCAG 2.1, PDF/UA (ISO 14289), and Section 508. Upload a PDF or enter a URL to a PDF document for instant analysis.

PDF Accessibility Checklist

Use this checklist to manually verify your PDF documents meet accessibility requirements:

What Makes a PDF Accessible?

A truly accessible PDF goes far beyond being "readable" on screen. It requires a hidden structure layer called a tag tree that defines every element's role and relationship. Screen readers like JAWS, NVDA, and VoiceOver rely entirely on this tag structure to announce content to users who are blind or have low vision. Without proper tags, a PDF is essentially an image — a visual layout with no semantic meaning whatsoever.

The core requirements for PDF accessibility are: a complete tag tree covering all content elements (paragraphs, headings, lists, tables, figures); a declared document language in the metadata (enabling correct pronunciation by text-to-speech engines); a logical reading order that matches visual presentation; meaningful alternative text for every image, chart, and figure; and color contrast ratios meeting WCAG 2.1 thresholds. The PDF/UA standard (ISO 14289) provides the most rigorous technical specification for these requirements, and meeting PDF/UA effectively satisfies WCAG requirements for PDF content.

PDF Accessibility Standards Compared

Three major standards govern PDF accessibility. Understanding how they relate helps you target the right compliance level for your organization:

How to Make a PDF Accessible: 8 Steps

Whether you're creating a new PDF or remediating an existing one, follow this sequence for reliable results:

1. Run a baseline accessibility check — Open the PDF in Adobe Acrobat Pro and run the full Accessibility Check (Tools → Accessibility → Full Check). This identifies the most common issues before you begin manual work.
2. Add or repair tags (Acrobat) — Use Tools → Accessibility → Add Tags to Document for untagged PDFs. For documents with incorrect tags, use the Reading Order tool to manually assign correct element types.
3. Set the document language — Go to File → Properties → Advanced → Reading Options and select the correct language. This enables screen readers to use the right pronunciation dictionary.
4. Add alternative text to all images — Right-click each figure in the Tags panel, select Properties, and enter a concise, meaningful description. Mark decorative images as Artifact so screen readers skip them.
5. Fix reading order — Use the Order panel (View → Navigation Panels → Order) to verify elements flow in the correct sequence. Drag items to reorder when the visual layout differs from the logical reading flow.
6. Fix table structure — Ensure tables have header cells (TH tags) and that the scope attribute correctly identifies row or column headers. Complex tables with merged cells require additional manual remediation.
7. Label all form fields — Each form field must have a tooltip or associated label. In Acrobat, right-click the field → Properties → General tab → Tooltip.
8. Re-check and screen reader test — Run the full accessibility check again. Then test with NVDA or VoiceOver, navigating through the document using heading navigation (H key), reading by line, and completing any forms.

Common PDF Accessibility Failures

An estimated 98% of publicly available PDFs on the web fail basic accessibility checks. The most frequent failures, in order of prevalence:

• Completely untagged PDF — Often the result of printing to PDF or exporting from software that doesn't support tagged output. The entire document is a flat image with no structure.
• Missing alt text on images — Charts, diagrams, logos, and photos without descriptions are invisible to screen reader users. Even decorative images need to be explicitly marked as artifacts.
• Incorrect reading order — Multi-column layouts, sidebars, and complex page designs frequently result in tag trees that read in the wrong sequence — mixing content from different columns or jumping between elements illogically.
• Scanned documents without OCR — A scanned PDF is just a photograph. Without Optical Character Recognition, there is no text layer at all. The document cannot be read by any assistive technology.
• Tables without header identification — Data tables where cells are tagged as TD (data) rather than TH (header) make it impossible for screen readers to announce column or row context.
• Missing document title — The Document Title field in metadata is announced by screen readers when the document opens. Using the filename as the title (e.g., "Q4-report-final-v2.pdf") is unhelpful and considered an accessibility failure.
• Insufficient color contrast — Gray text on white, yellow on light backgrounds, and low-contrast chart legends fail the 4.5:1 minimum contrast ratio required for normal text.
• Unlabeled form fields — Form fields without tooltips or labels present as anonymous boxes to screen reader users, making form completion impossible without sighted assistance.

PDF Checker Tools Compared

Several tools are available to check PDF accessibility. Here is an honest comparison of the main options:

PAC 2024, developed by the Swiss Foundation Access for All, remains the most thorough dedicated PDF accessibility checker. Its limitation is Windows-only availability. For Mac users, Adobe Acrobat Pro's built-in checker is the most accessible option despite its subscription cost. Our website accessibility scanner checks linked PDFs for fundamental properties as part of the broader site audit.

Who Needs PDF Compliance?

PDF accessibility obligations vary by organization type, but the trend is toward universal coverage:

• Federal agencies — Section 508 of the Rehabilitation Act mandates accessible electronic documents for all federal agencies. This includes all PDFs published on .gov websites, used in procurement, or shared internally.
• State and local government — ADA Title II covers state and local government entities. The DOJ's 2024 final rule extends WCAG 2.1 AA requirements to all digital content, including PDFs published on government websites.
• Private businesses (Title III) — Courts have ruled that PDFs linked from websites covered by ADA Title III must themselves be accessible. Retail, healthcare, financial services, and real estate firms face significant exposure for inaccessible PDFs (leases, contracts, product manuals, invoices).
• Educational institutions — Section 504 of the Rehabilitation Act and the Americans with Disabilities Act both require educational materials to be accessible. Universities, colleges, and K-12 schools face OCR (Office for Civil Rights) complaints for inaccessible PDFs including syllabi, course materials, and forms.

Frequently Asked Questions