Deadline guide
ADA Title II and PDF accessibility: the 2027–2028 deadlines
The Department of Justice’s ADA Title II rule makes WCAG 2.1 Level AA the technical standard for web content published by state and local governments — including the PDFs on their websites. Here is what the rule requires, when it applies, and where documents fit.
What the ADA Title II rule requires
In April 2024, the DOJ published a final rule (28 CFR Part 35) requiring state and local governments to make their web content and mobile applications conform to WCAG 2.1 Level AA. The rule applies to public entities: state agencies, counties, cities, towns, school districts and special district governments.
“Web content” is broad. It includes the pages of a website, online forms, documents posted for download, and content delivered through a mobile app. A PDF linked from a public page is web content. Posting the PDF and assuming the page around it is accessible does not satisfy the requirement.
The rule does not replace the rest of the ADA. Public entities still have an independent obligation to provide effective communication and reasonable modifications, including auxiliary aids and services, on request.
The compliance dates
| Entity population | Compliance date | What it means for documents |
|---|---|---|
| 50,000 or more people | April 26, 2027 | New and existing web content, including published PDFs, should conform to WCAG 2.1 AA. |
| Fewer than 50,000 people, and special district governments | April 26, 2028 | The same standard applies, with an additional year to comply. |
Population is generally based on the most recent census data available. A public entity should confirm its category and any local or state obligations with counsel.
On April 20, 2026, DOJ published an interim final rule that extended both compliance dates by one year, from April 24, 2026 to April 26, 2027 for entities with a total population of 50,000 or more, and from April 26, 2027 to April 26, 2028 for smaller entities and special district governments. The rule took effect immediately; the underlying WCAG 2.1 AA obligation is unchanged.
Which PDFs are covered?
Start with the documents people need in order to:
- apply for, renew or appeal a public benefit or licence;
- pay a tax, fee or fine;
- find meeting agendas, minutes, budgets and financial reports;
- participate in a public hearing or procurement;
- understand a public health, safety or emergency notice;
- exercise a right or file a complaint.
Those documents are the highest risk and the highest value. Historical archives, newsletters and purely informational material can usually be scheduled later — subject to the exceptions below and to requests for accommodation.
The exceptions, and their limits
The final rule includes exceptions, but they are narrower than they sound. Commonly discussed exceptions include:
- Archived web content. Content kept only for reference, not changed after archiving, and not used to access a service.
- Preexisting conventional electronic documents. Documents posted before the compliance date, subject to conditions in the rule.
- Third-party content. Content posted by a third party that the public entity does not control.
- Individualised documents. Documents about a specific person, such as a personalised letter.
- Password-protected course content. Content for enrolled students in a course.
An exception from WCAG conformance is not an exemption from the ADA. If a person needs a document to access a service, the public entity may still have to provide an accessible version or another effective accommodation. Do not use an exception as a reason to leave a high-use form inaccessible.
What to do now
- Inventory the documents. Crawl the site and record PDFs, page counts, owners, last-modified dates and whether each file has a text layer.
- Rank by risk. Forms and service documents first, then high-traffic reports, then archives.
- Fix the source templates. Stop producing new inaccessible PDFs. Fix the authoring templates before remediating the backlog.
- Remediate or provide an accessible alternative. Remediate the forms and high-use documents; publish structured transcripts for long reports and archives.
- Publish an accessibility statement. State the standard you are targeting, how to request an accommodation, and how to report a barrier.
- Test with real assistive technology. Keyboard-only operation and a screen-reader pass catch problems that checkers miss.
- Schedule re-review. Documents change. Put remediation dates and owners in the same system as the documents.
Where Remediate fits
Remediate is a remediation layer for documents you already publish. The original PDF stays available; alongside it, the viewer provides a structured transcript with headings, tables, alt text, reading aids, translation and cited answers. That gives readers an accessible path without waiting for a full archive re-authoring project.
It is not a substitute for legal advice, and it does not by itself certify a document as conforming. It is a way to make the content usable now while a team works through the archive. See how PDF remediation works and the reviewer checklist.
Frequently asked questions
When is the ADA Title II deadline for PDFs?
Public entities with a total population of 50,000 or more have a compliance date of April 26, 2027. Public entities with a total population of fewer than 50,000, and special district governments, have a compliance date of April 26, 2028. DOJ extended both dates by one year in an interim final rule published April 20, 2026.
Do ADA Title II rules apply to PDFs?
Yes. The rule covers web content, and PDFs posted on a public entity website are web content. The technical standard is WCAG 2.1 Level AA, which includes document structure, reading order, alt text, tables, forms and contrast.
Are all historical PDFs covered immediately?
The rule includes exceptions for archived content and certain preexisting documents, with conditions. High-use documents and anything needed to access a service still require an effective accessible path. Confirm the details with counsel.
Does a tagged PDF satisfy ADA Title II?
Not necessarily. Tags must be correct: reading order, heading levels, table headers, alt text, form labels and language metadata all need review. Automated tagging alone is rarely enough.
What if we cannot remediate the whole archive in time?
Prioritise forms, notices and high-traffic documents; publish accessible alternatives for long reports; document the plan and the accommodation process; and keep a dated remediation queue. A credible, resourced plan is better than an unverified claim of compliance.
This guide is general information, not legal advice. Confirm your obligations with counsel and your accessibility office.