ADA Title II and PDFs: what small governments need to know
The Department of Justice rule under Title II of the Americans with Disabilities Act requires state and local government web content, including documents such as PDFs, to meet WCAG 2.1 Level AA, subject to the rule's exceptions and limits. This page summarises it for small bodies. It is general information, not legal advice, and this site's checker does not determine whether you meet the rule.
Deadlines as published
The rule (28 CFR 35.200) sets April 26, 2027 for public entities with a population of 50,000 or more, and April 26, 2028 for smaller entities and for all special district governments. The Department of Justice moved these dates once already: an interim final rule published April 20, 2026 extended them from April 24, 2026 and April 26, 2027. Confirm the current dates on ada.gov before relying on them.
Which documents are covered
The rule has exceptions, and they are narrower than many people assume. They include archived web content (only if all four conditions in the rule are met), preexisting conventional electronic documents, content posted by a third party (not if it is posted under a contract or license with you), and individualized password-protected documents. The exceptions do not remove the duty to provide accessible formats on request.
The preexisting-document exception does not apply to documents that are currently used to apply for, gain access to, or participate in your services. DOJ's own examples: an application for a current city program probably must comply, while older council minutes likely fall within the exception. Whether a fee schedule, permit form or packet is covered depends on whether people currently use it to access services.
Why new documents matter most
New content posted after your compliance date must meet WCAG 2.1 AA unless an exception or the rule's fundamental-alteration and undue-burden limits apply. Even if an old archive may be exempt, the stream of new agendas, minutes, notices and forms is not. The practical approach is to fix the process that creates documents, so each new PDF is accessible at export, and then work back through the documents residents actually use.
A suggested approach (not a legal requirement)
- Inventory the documents on your website and sort them by how often residents use them.
- Check them with an automated checker to find the obvious failures: missing tags, no language, scans with no text.
- Fix the source documents (usually Word) and re-export, rather than repairing each PDF by hand.
- Have a person check reading order and alternative text on the most important documents.
- Publish a way for residents to report a problem and name a contact who responds.
DOJ describes its own action steps as suggestions, not requirements.
Questions
Does passing an automated check mean we comply?
No. Automated checks find only some problems. Reading order, meaningful alt text and link text need a person to review.
Can an overlay or plugin make our site compliant?
Be cautious. The FTC took action against one overlay vendor (accessiBe, final order April 2025, $1 million) for unsupported claims that its automated tool makes sites WCAG-compliant. Fix the documents themselves.
Guides last checked 2026-10-18. General information, not legal advice. Menu names can differ between software versions.