Under the DOJ's ADA Title II rule, state and local government web content — including PDFs — must meet WCAG 2.1 Level AA. After the 2026 interim final rule, the deadlines are April 26, 2027 for public entities of 50,000+ and April 26, 2028 for smaller entities and special districts. Here's how to actually make a PDF ADA-compliant.
What "ADA-compliant PDF" means in practice
The rule points at WCAG 2.1 AA; for PDF documents the machine-checkable target is PDF/UA-1 (ISO 14289-1). A compliant PDF has a real tag tree, a document title and language, alt text on figures, logical reading order, and labeled tables and form fields. See the full ADA Title II requirements and deadlines.
The 4-step remediation workflow
- Inventory. List every public-facing PDF. Most entities find 3–10× more than expected — reports, agendas, forms, board minutes, maps.
- Validate. Run each document through a PDF/UA-1 validator (veraPDF) or our free checker to get a machine-readable failure list. This is your work queue.
- Remediate. Fix the deterministic failures programmatically — tag tree, metadata, reading order, figure tagging. Auto-remediation returns a compliant PDF plus a veraPDF validation report in about 60 seconds.
- Document. Keep the validation reports. They're your good-faith compliance evidence if a complaint or audit arises.
What must be fixed
The same failures recur across nearly every document library:
- Missing tag tree — screen readers receive raw content with no structure
- No document title, language, or "tagged" flag
- Figures without alt text
- Broken reading order — multi-column layouts reading across instead of down
- Tables and forms — headers not marked, fields unlabeled
Our compliance checklist covers each one in detail.
What about archived PDFs?
Documents kept solely for reference can qualify for the archived-content exception. But anything still used to apply for, access, or participate in a program or service must conform. When in doubt, remediate — remediating under a consent decree is always more expensive than remediating on your own schedule. Demand letters commonly settle in the $5,000–$75,000 range plus legal fees.
Cost and scale
Manual remediation services quote around $5.50 per page — $110 for a 20-page document, with days of turnaround. Automated remediation to the same PDF/UA-1 standard runs about $2.99 per document flat, or unlimited with membership for whole libraries. For the volume most public entities face, the difference is order-of-magnitude. See the full cost breakdown.
Start with one document
Run your worst PDF through the free checker. If the report isn't useful, you've lost 30 seconds. If it is, you have your remediation roadmap — and the first fixed document ships with a validation report as evidence.
This is technical guidance, not legal advice. For counsel on your specific obligations, talk to an attorney familiar with ADA digital accessibility.
Sources and references
- ADA.gov — Web Accessibility Guidance
- Federal Register — ADA Title II Interim Final Rule (FR Doc. 2026-07663)
- ISO 14289-1:2014 — PDF/UA-1
- W3C — WCAG 2.1
Real-world scenario: a city government's document library
Consider a mid-sized city with 120,000 residents. Their ADA Title II compliance audit discovered 4,700 public-facing PDFs — meeting minutes, budget reports, building permit forms, park brochures, city council agendas. All were visually formatted, none were tagged. Manual remediation at $5.50 per page would cost tens of thousands and take the better part of a year. Here is what the four-step workflow looks like at that scale:
- Inventory (Week 1). An automated crawl of the city's .gov domain surfaced every PDF linked from a public page. The raw list: 4,700 documents, ranging from 1 to 85 pages.
- Validate (Week 1–2). Batch-validation with veraPDF produced a per-document failure report. Result: 4,680 documents failed PDF/UA-1. Only 20 documents — those generated from accessible InDesign templates — passed on the first check.
- Remediate (Week 2–4). Automated remediation handled the structural failures on the high-priority documents (agendas, forms, reports for the current year) in about a minute each. A human reviewer spot-checked alt-text quality on budget charts and complex forms. The total cost: approximately $2.99 per document for the fixed ones, not $5.50 per page.
- Document (ongoing). Each fixed document shipped with its post-remediation veraPDF report — stored alongside the PDF in the city's CMS as accessible compliance evidence. The remaining library is being processed by priority tier.
What auditors look for — and what you should keep
In an ADA Title II compliance review or audit, expect questions about three things: (1) your document inventory — do you know what you have, (2) your validation evidence — can you show per-document reports, and (3) your remediation log — what was fixed, when, and against what standard. A veraPDF validation report answers all three: it identifies the document, lists every failure, records the ISO clause for each, and provides a dated artifact. Keep these files. They turn "we think we're compliant" into "here is the machine-checked evidence."
Prioritizing your document library
Not every PDF needs remediation on the same timeline. Split your library into three tiers:
- Tier 1 — Essential services. Forms, applications, permit documents, public notices. These are how residents interact with your entity. No one should need assistance to fill out a form. These go first.
- Tier 2 — Informational content. Reports, agendas, meeting minutes, budget documents, policy statements. These communicate decisions and data. They should be accessible, but a 2019 annual report is less urgent than a current-year building permit.
- Tier 3 — Archived reference. Historical documents kept for legal or archival reasons. These may qualify for the archived-content exception, but if they are still discoverable and usable by the public, the safest path is to remediate or clearly mark them as archival and provide an accessible alternative on request.
For a detailed walkthrough of the validation and triage process, see how to check if a PDF is accessible.