PDF Accessibility: How to Make ADA-Compliant PDFs

1. Why PDF Accessibility Matters Now

PDFs are everywhere in government and business — forms, reports, policies, meeting minutes, financial statements, contracts, educational materials. The problem? The vast majority of them are completely inaccessible to people who use screen readers, keyboard navigation, or other assistive technologies.

When a screen reader encounters an untagged PDF, it often reads gibberish — characters out of order, columns mixed together, images with no descriptions, and tables that make no sense. For the more than 1 in 4 U.S. adults living with a disability, inaccessible PDFs don't just create inconvenience — they block access to essential services, information, and opportunities.

The urgency is real. Ohio State University has budgeted $20 million for PDF remediation alone. The state of Texas reports that agencies and universities are actively working on PDF remediation as part of their ADA Title II compliance push. A NASCIO survey found that 54% of state CIOs have no dedicated funding for accessibility services — yet they face an April 24, 2026 compliance deadline that explicitly covers electronic documents.

And it's not just government. Businesses face growing litigation risk. In the 8,667 ADA website lawsuits filed in 2024, inaccessible documents — particularly PDFs — were cited as barriers in financial services, healthcare, and higher education cases. When a bank puts its account disclosures in an inaccessible PDF, or a hospital publishes patient forms that screen readers can't navigate, they're creating both a legal liability and a real barrier for real people.

2. Legal Requirements for Accessible PDFs

Multiple laws and standards require PDF accessibility. Here's how they apply:

ADA Title II — State and Local Government

The DOJ's April 2024 final rule requires all web content — including electronic documents like PDFs — to meet WCAG 2.1 Level AA. This covers:

• PDFs posted on government websites (forms, reports, agendas)
• PDFs sent via email as part of government services
• PDFs in online portals (permit applications, tax forms)
• Meeting minutes, budget documents, policy manuals
• Educational materials at public universities and K-12 schools

Failure to comply can trigger DOJ enforcement actions, including compensatory damages, mandatory injunctive relief, and civil penalties of up to $75,000 for a first violation and $150,000 for subsequent violations (inflation-adjusted).

ADA Title III — Private Businesses

While the DOJ hasn't issued a specific Title III web rule, federal courts increasingly hold that digital content, including PDFs, must be accessible. This is particularly enforced in:

• Financial services: Account statements, disclosures, loan documents
• Healthcare: Patient intake forms, insurance explanations, lab results
• E-commerce: Product manuals, return policies, terms of service
• Education: Course materials, syllabi, registration forms

Section 508 — Federal Government

Section 508 of the Rehabilitation Act requires federal agencies to make all electronic and information technology accessible, including PDFs. The standard references WCAG 2.0 Level AA (updated guidance aligns with WCAG 2.1). The FY2024 assessment found federal agencies' average conformance score was just 1.74 out of 5 — with document accessibility being one of the weakest areas.

European Accessibility Act (EAA)

For organizations operating in Europe, the European Accessibility Act (enforced since June 2025) requires accessible digital content for products and services sold in the EU. PDF accessibility applies to banking, e-commerce, transportation, and telecommunications providers serving EU customers.

3. What Makes a PDF Accessible?

An accessible PDF isn't just a document that "looks right" on screen. It's a document with an underlying structure that assistive technologies can interpret. Here are the core requirements:

4. Understanding Tagged PDF Structure

Tags are the foundation of PDF accessibility. They're metadata elements embedded in the PDF file that define the document's logical structure — think of them as the HTML equivalent for PDFs.

When you open a tagged PDF in Adobe Acrobat's Tags panel, you see a tree structure similar to an HTML DOM. Each tag identifies what an element is: a heading, paragraph, list item, table cell, figure, link, or form field.

Essential PDF Tag Types

Tagged vs. Untagged PDFs

You can check if a PDF is tagged in Adobe Acrobat by going to File → Properties → Description and looking for "Tagged PDF: Yes." But having tags doesn't guarantee correct tags. Auto-generated tags from Word exports often have incorrect heading levels, missing table headers, and poor reading order — all of which require manual review and correction.

A truly accessible tag tree has:

• Correct hierarchy: H1 → H2 → H3 (no skipping from H1 to H3)
• All content tagged: No text floating outside the tag tree
• Artifacts marked: Page numbers, decorative lines, watermarks excluded from reading
• Matching reading order: Tag order matches visual layout
• Proper nesting: List items inside lists, cells inside rows inside tables

5. How to Create Accessible PDFs from Scratch

The most cost-effective approach to PDF accessibility is to create accessible documents from the start. Retrofitting accessibility onto an existing PDF is 3-10x more expensive than building it in from the beginning.

From Microsoft Word

Microsoft Word is the most common source for PDFs, and it can produce well-tagged PDFs if you follow these practices:

1. Use built-in heading styles (Heading 1, Heading 2, etc.) — don't just make text bold and large. Screen readers rely on heading tags for navigation.
2. Use Word's list tools for bulleted and numbered lists — don't manually type "1." or "•". Manually formatted lists don't export as tagged lists.
3. Add alt text to all images via right-click → "Edit Alt Text." Mark decorative images as "Mark as decorative."
4. Use Word's table tools for tables. Define header rows via Table Properties → Row → "Repeat as header row at the top of each page."
5. Use meaningful hyperlink text — "Read the full report" instead of "click here" or a bare URL.
6. Set the document language in File → Options → Language.
7. Run the built-in accessibility checker via Review → Check Accessibility before exporting.
8. Export properly: Use File → Save As → PDF (not Print → PDF, which creates an image-based PDF). Check "Document structure tags for accessibility" in the options.

From Google Docs

Google Docs' PDF export has improved but still lags behind Word:

• Use built-in heading styles (Normal, Heading 1-6)
• Add alt text to images (right-click → "Alt text")
• Export via File → Download → PDF. Tags are generated automatically.
• Limitation: Google Docs doesn't properly export table headers, complex lists, or language attributes. Always validate the exported PDF and plan for manual remediation of tables.

From Adobe InDesign

InDesign is used for complex layouts (reports, brochures, magazines) and offers strong PDF accessibility support:

• Map paragraph styles to PDF tags (Object → Object Export Options)
• Set reading order via the Articles panel (Window → Articles)
• Add alt text via Object → Object Export Options → Alt Text tab
• Export with "Create Tagged PDF" checked and "Use Structure for Tab Order" enabled
• Complex multi-column layouts require careful Articles panel ordering

From LaTeX

LaTeX is widely used in academia and scientific publishing. Producing accessible PDFs from LaTeX has historically been extremely difficult, but the tagpdf package (developed by the LaTeX Project) is making progress. Currently:

• Basic tagging works for simple documents (headings, paragraphs, lists)
• Math equations remain a major challenge — MathML support is limited
• Complex scientific documents typically need post-processing in Acrobat
• Consider HTML output as an accessible alternative (via pandoc or lwarp)

6. How to Remediate Existing PDFs

Most organizations face a backlog of inaccessible PDFs that need remediation. Here's the systematic process:

Step 1: Run the Accessibility Checker

In Adobe Acrobat Pro: All Tools → Prepare for Accessibility → Check for Accessibility. This identifies missing tags, reading order issues, missing alt text, and form field problems. Address each issue systematically.

Step 2: Add or Fix Tags

Open the Tags panel (View → Navigation Panels → Tags). If the PDF has no tags, use "Add Tags to Document" for auto-tagging, then correct the results. For each element:

• Verify heading levels are correct and hierarchical
• Ensure paragraphs are tagged as <P>, not <Span>
• Convert decorative elements to artifacts
• Fix any content tagged as the wrong element type

Step 3: Fix Reading Order

Use the Reading Order tool (All Tools → Prepare for Accessibility → Set Reading Order) or the Order panel. Walk through the document page by page, verifying that numbered regions flow in the correct sequence. Multi-column layouts, sidebars, and pull quotes often have incorrect order.

Step 4: Add Alternative Text

Right-click each Figure tag → Properties → Tag → Alternative Text. Write descriptions that convey the meaning and purpose of the image, not just what it looks like. For charts: describe the trend or key data points. For diagrams: describe the relationships shown.

Step 5: Fix Table Structure

This is often the most time-consuming step. For each table:

• Verify header cells are tagged as <TH> (not <TD>)
• Set scope attributes (Row or Column) on header cells
• For complex tables with merged cells: add ID/Headers attributes
• Consider using the Table Editor in Acrobat's accessibility tools

Step 6: Set Document Properties

• Set document title (File → Properties → Description → Title)
• Set language (File → Properties → Advanced → Language)
• Set "Initial View" to show Document Title in title bar (not filename)
• Add bookmarks matching heading structure for documents 20+ pages

Step 7: Test with Assistive Technology

Automated checks catch structure issues but miss usability problems. Test with:

• NVDA (free) or JAWS — listen to the full document read-through
• Keyboard-only navigation — tab through all links and form fields
• Reflow mode (View → Zoom → Reflow) — verify content reflows correctly

7. Making Scanned PDFs Accessible

Scanned PDFs — documents created by scanning paper — are the hardest to remediate because they're essentially photographs. Screen readers see nothing but a flat image. The process requires:

Step 1: OCR Processing

Run Optical Character Recognition to extract text from the scan. In Acrobat: All Tools → Scan & OCR → Recognize Text. Choose "Searchable Image (Exact)" to preserve visual layout while adding a text layer. OCR quality depends on:

• Scan resolution: 300 DPI minimum, 600 DPI preferred
• Original print quality: Clean type produces 95%+ accuracy; faded or damaged documents may be 70-80%
• Language and fonts: Standard fonts in major languages work well; handwriting, unusual fonts, and mixed-language documents are challenging
• Layout complexity: Simple single-column documents OCR well; multi-column with images requires manual correction

Step 2: Verify OCR Accuracy

OCR is never 100% accurate. Review the extracted text, paying special attention to:

• Numbers and dates (commonly misread)
• Proper nouns and technical terms (not in OCR dictionaries)
• Characters confused by OCR: l/1/I, O/0, rn/m, cl/d
• Tables and columnar data (columns often merge or split)

Step 3: Tag and Remediate

After OCR, follow the standard remediation process (Section 6 above). Auto-tagging after OCR typically produces lower-quality tags than tagging a natively digital PDF, so budget extra time for manual corrections.

8. PDF Accessibility Testing Tools

Testing requires both automated checking and manual verification with assistive technology. Here are the essential tools:

9. Most Common PDF Accessibility Failures

Based on data from accessibility audits across government agencies, universities, and businesses, these are the most frequently encountered PDF accessibility failures:

10. PDF/UA Standard Explained

PDF/UA (Universal Accessibility) is the ISO standard (ISO 14289) specifically for accessible PDF documents. While WCAG provides general web accessibility guidelines, PDF/UA defines precise technical requirements for how PDF structure must be built.

PDF/UA-1 (ISO 14289-1:2014)

The first version, based on PDF 1.7. Key requirements:

• All content must be tagged (no untagged content)
• Tags must use the PDF 1.7 standard structure types (or map to them)
• All multimedia and alternative representations must be provided
• Document metadata (title, language) must be set
• Security settings must not interfere with assistive technology

PDF/UA-2 (ISO 14289-2:2024)

The updated version, published in 2024 and based on PDF 2.0. Major improvements:

• Better WCAG alignment: Requirements map more directly to WCAG 2.x success criteria
• MathML support: Native mathematical formula accessibility (critical for STEM documents)
• Enhanced structure types: More precise tag types for common document elements
• Pronunciation: Support for pronunciation dictionaries
• Annotations: Better handling of comments, notes, and redactions

11. PDF Remediation Cost Breakdown

PDF remediation costs vary dramatically based on document complexity, volume, and source quality. Here's what to expect:

Per-Page Cost Ranges

Volume Discounts

Remediation vendors typically offer 20-40% discounts for bulk projects:

• 1-50 documents: Standard per-page rates
• 50-500 documents: 20-30% volume discount
• 500+ documents: 30-40% discount + dedicated project management

Real-World Cost Examples

The IRS Disabled Access Credit (Form 8826) allows small businesses to claim up to $5,000 annually for accessibility expenditures, including PDF remediation costs. The credit covers 50% of eligible expenses between $250 and $10,250.

12. Government Agency PDF Compliance

Government agencies face unique challenges with PDF accessibility — massive document libraries, limited budgets, and a hard compliance deadline.

The Scale of the Problem

According to the NASCIO 2026 compliance report:

• Only one state (as of July 2025) had fully implemented a compliance plan
• 54% of state CIOs reported no dedicated funding for accessibility services
• 34% of states lack dedicated IT accessibility coordinators
• Vendor procurement and contracted services create fragmented governance

State Success Stories

NASCIO's Priority Recommendations

1. Start with governance: Clarify roles and secure stakeholder buy-in
2. Hire an accessibility coordinator: The "most vital part" of enterprise compliance
3. Embed in procurement: Require accessibility in vendor contracts
4. Prioritize high-impact systems: Don't try to fix everything at once
5. Shift left: Build accessibility into design and development, not just remediation

13. Prioritization Framework

With potentially thousands of PDFs to remediate, prioritization is critical. Use this framework to decide what to fix first:

Tier 1: Immediate (Fix Within 30 Days)

• Forms required to access services — applications, registrations, complaints, requests
• High-traffic documents — anything with 100+ downloads/month
• Legal/rights documents — policies, terms, contracts, notices
• Currently-linked from homepage or main navigation

Tier 2: Short-Term (Fix Within 90 Days)

• Regular publications — newsletters, reports, agendas, minutes
• Educational materials — course documents, guides, handbooks
• Financial documents — budgets, audits, annual reports

Tier 3: Medium-Term (Fix Within 6 Months)

• Historical publications — older reports and documents still linked
• Marketing materials — brochures, flyers, fact sheets
• Supporting documents — appendices, supplementary data

Tier 4: Ongoing / On-Request

• Deep archives — documents from 5+ years ago with minimal access
• Superseded documents — old versions replaced by current content
• Third-party content — documents from vendors or partners

14. PDF Accessibility Tools Compared

Here's how the major PDF accessibility tools compare for different use cases:

For Creating Accessible PDFs

For Remediating Existing PDFs

For Testing/Validating PDFs

15. Complete PDF Accessibility Checklist

Use this checklist for every PDF you create or remediate:

16. Frequently Asked Questions

Related Guides