ADA Compliant PDF: What the Rule Requires
On this page
There is no such thing as an “ADA compliant PDF” in the sense of a certificate or a seal. Compliance is a judgement about whether the documents your entity publishes meet the accessibility standard the rule references, which for public entities is WCAG 2.1 AA, and it is judged on the set of documents you make available, not on a single file. What you can do is make each PDF meet the standard and keep a record of how.
What does the ADA actually say about documents?
The rule that matters here is the DOJ’s web and mobile app accessibility rule under ADA Title II. It requires state and local government entities to meet WCAG 2.1 AA for their web content, and that requirement reaches the documents those entities publish, PDFs included. The DOJ published an interim final rule in April 2026 extending the compliance dates, and its own resource is at the DOJ web rule.
Two things follow. First, the standard is WCAG 2.1 AA (the WCAG 2.1 specification), not a separate PDF rule, though PDF/UA is the PDF-specific standard that gets you there. Second, the obligation is about your published content, so a folder of internal drafts is a different problem from the PDFs linked from your public site.
What are the 2027 and 2028 deadlines?
| Entity | Compliance date |
|---|---|
| Public entities serving 50,000+ people | 26 April 2027 |
| Smaller entities and special district governments | 26 April 2028 |
The dates come from the DOJ’s interim final rule published in April 2026. If you are a city, county, school district, public university or special district, one of those two dates is yours. Section 508 applies separately to federal agencies and to vendors selling to them, and the European Accessibility Act has applied since 28 June 2025 to services in scope in the EU. Those are covered in the Section 508 PDF guide and the European Accessibility Act guide.
The practical effect of the 2027 date is a deadline that is close enough to plan against and far enough to do the work, which is exactly why so many coordinators are inventorying PDFs now.
Is WCAG 2.1 AA the right yardstick for a PDF?
Yes, for public-sector work. WCAG is written for web content, and a PDF published on a web page is web content. The criteria that bite hardest on PDFs are:
- 1.1.1, text alternatives for images.
- 1.3.1, information and relationships, which for a PDF means the tag structure.
- 1.3.2, a meaningful reading sequence.
- 2.4.2, a page or document title.
- 3.1.1, the language of the document.
A correctly tagged PDF with real alt text, a logical reading order, a language and a title meets all five. The WCAG and PDFs guide maps each criterion to what you do in the file, and the accessible PDF checklist turns it into a per-file list.
Who else does this rule touch?
Public entities are not alone in this. Vendors and contractors who produce documents for a city, county or school district often publish PDFs that carry the entity’s obligations, and a good contract now asks for accessible deliverables rather than fixing them after the fact. The same is true on the federal side, where Section 508 reaches vendors selling to agencies. If you write or design documents for public-sector clients, the practical move is to build them accessibly from the start: real heading styles, alt text and a document title before export, which is what the accessible PDF checklist covers.
What do I do about a legacy archive?
The archive is where compliance programs stall, because it can be thousands of files and none of them have a source document. A workable approach:
- Inventory. List the PDFs your site links to, with the page they are linked from and how often they are downloaded if you can measure it.
- Prioritise by risk. Current, transactional and frequently used documents first; then anything named in a complaint or a records request; then the long tail.
- Triage, do not perfect. A file that reads correctly with a screen reader is worth more than a file with a flawless checker report that took a week.
- Fix at scale where you can. For routine files with no source, a hosted tool tags them in one pass and returns a report of what still needs a human, so a person only touches the flagged items.
- Record what you did. A register of file, date, method and result is your defence and your plan.
Triage is the whole game for an archive. A remediation aid such as TagRight is built for exactly this: it tags a PDF you did not author, leaves the pages looking the same, and names what it could not fix rather than pretending. It is not a certification, and a binding or high-stakes document should still be verified with PAC 2024 or veraPDF. For the full picture of how the standard works, start with the PDF accessibility guide, and if you have the source, the cheapest fix is an export from Word or Docs.
The free tier for the hosted route is on the pricing page. To see what a tagged file and its report look like on one of your own documents, you can tag a PDF free.
Frequently asked questions
Is there an ADA compliant PDF certificate?
No. There is no certificate, seal or badge that makes a PDF ADA compliant. Compliance is judged on whether the documents you publish meet the accessibility standard the rule references, which in practice is WCAG 2.1 AA, and it is judged on the published document set rather than a single file.
What does the ADA Title II rule require for PDFs?
The DOJ's web rule requires state and local government entities to meet WCAG 2.1 AA for their web content, and that covers the documents they publish, PDFs included. The interim final rule published in April 2026 set the compliance dates at 26 April 2027 and 26 April 2028 depending on entity size.
When is the ADA compliance deadline?
For public entities serving 50,000 or more people, the DOJ set 26 April 2027. For smaller entities and special district governments, it is 26 April 2028. Both come from the interim final rule published in April 2026.
Do I have to remediate every PDF I have ever published?
The rule covers the documents your entity publishes and makes available. In practice teams prioritise: current and high-traffic documents first, then the archive by risk. A defensible, documented plan matters more than an impossible attempt to fix everything at once.
Is a tagged PDF automatically ADA compliant?
No. Tagging is necessary but not sufficient. A file also needs meaningful alt text, a correct reading order and a real document title. Tagging is the foundation the rest sits on.