The ADA Title II web accessibility rule, explained for documents
In April 2024 the Department of Justice finalized a rule under ADA Title II (28 CFR Part 35, subpart H) requiring state and local governments to make web content, including PDFs and documents, conform to WCAG 2.1 Level AA. If your entity serves 50,000 or more people, your deadline is April 26, 2027; smaller entities and all special districts have until April 26, 2028.
- 50,000 or more
- 7 months to April 26, 2027
- Under 50,000 and special districts
- 19 months to April 26, 2028
Whole months from September 21, 2026. Find your entity's date.
The rule
What is the ADA Title II web accessibility rule?
It is a Department of Justice regulation, published in the Federal Register on April 24, 2024, that sets WCAG 2.1 Level AA as the enforceable standard for state and local governments' web content and mobile apps — the standard your documents must now meet. It sits in the Title II regulation as subpart H of 28 CFR Part 35.
Title II has required equal access to government programs and services since 1990. What changed in 2024 is precision: instead of a general obligation, the rule names a testable standard (WCAG 2.1 Level AA), sets compliance dates, and spells out which of your content — including documents — is covered and which narrow exceptions apply. The Department extended those dates by one year in an interim final rule published April 20, 2026 (91 FR 20902); the standard and the scope were not changed, and the Department says it plans further rulemaking on the substance of the 2024 rule.
Who is covered
Who must comply with ADA Title II?
All state and local government entities must comply, regardless of size or budget: cities, counties, townships, state agencies and courts, public school districts, public colleges and universities, and special districts such as transit, water, library, park and housing authorities. Federal agencies and private businesses are covered by other laws, not Title II.
| Entity type | Covered by Title II | Their workflow |
|---|---|---|
| Public school districts, including charter schools that are public entities | Yes | School districts |
| Public colleges, community colleges and universities | Yes | Higher education |
| Cities, counties, towns and townships | Yes | Cities and counties |
| State agencies, courts and legislatures | Yes | State agencies |
| Special districts: transit, water, library, park, housing and other authorities | Yes | Special districts |
| Federal agencies | No — Section 508 | Section 508 |
| Private businesses | No — other law |
Contractors and vendors do not take the obligation away: content a third party posts or maintains for a public entity is covered as if the entity had posted it itself.
Documents
Does the rule cover PDFs and other documents?
Yes. The rule's definition of web content expressly includes documents — PDF files, word processor files, presentations and spreadsheets — that a public entity makes available through a website or mobile app. Your public-facing documents must conform to WCAG 2.1 Level AA just like an HTML page, unless a specific exception applies.
For a typical PDF that means, at minimum: a tagged structure with a correct reading order, a document title and language setting, alternative text on meaningful images, labeled form fields, sufficient contrast in the text layer, and tables tagged with headers. Scanned image-only PDFs fail all of this by default and need OCR plus tagging before they can conform.
Exceptions
Which documents are exempt? The archived-content and preexisting-document exceptions
Two exceptions matter most for documents: archived web content and preexisting conventional electronic documents. Both are narrower than they sound. A document already posted before your compliance date is excepted unless it is currently used to apply for, gain access to, or participate in a service, program or activity; archived content is excepted only while it is kept solely for reference, research or recordkeeping.
| Condition | Archived web content | Preexisting conventional electronic documents |
|---|---|---|
| What it covers | Any web content, including documents | PDF, word processor, presentation and spreadsheet files |
| Created or posted before the compliance date | Required | Required |
| Kept solely for reference, research or recordkeeping | Required | Not required |
| In a dedicated area identified as archived | Required | Not required |
| Unaltered since archiving | Required | Does not apply |
| Lost if currently used to apply for or access a service | Does not apply | Yes |
| Lost if reposted or updated | Yes | Yes |
A decision path. First: was it posted before your compliance date? No means it must conform to WCAG 2.1 AA. Second: is it currently used to apply for, gain access to or take part in a service? Yes means it must conform. Third: is it kept only for reference, research or recordkeeping, in a dedicated area identified as archived, and unaltered since? Yes means the archived-content exception applies; no means a PDF or Office file may qualify as a preexisting conventional electronic document while other content must conform. The path is a guide to the questions, not a determination.
Archived web content
Content qualifies only if all four conditions hold: it was created before the entity's compliance date (or reproduces paper or other physical records created before it), it is retained exclusively for reference, research or recordkeeping, it sits in a dedicated area clearly identified as archived, and it has not been altered or updated since it was archived. Reposting or updating a file ends the exception.
Preexisting conventional electronic documents
PDF, word processor, presentation and spreadsheet files that were already available on the entity's site or app before its compliance date are excepted — unless the document is currently used to apply for, gain access to, or participate in the entity's services, programs or activities. A permit application form, a school enrollment packet or a current bus schedule cannot rely on this exception, no matter when it was posted. Unlike the archived-content exception, this one does not require a dedicated archive area.
The limits in practice
The exceptions never cover documents published from your compliance date on, and they do not switch off Title II's general obligations: a person can still ask for an accessible version of excepted content, and you still have to provide effective communication. Treat the exceptions as a way to sequence remediation of a large backlog — starting with what people use — not as a reason to skip counting it.
Enforcement
How is the ADA Title II rule enforced?
Through the same channels as the rest of the ADA: individuals can file complaints with the Department of Justice or sue a public entity directly, and the DOJ can investigate and litigate. The 2024 rule added no new enforcement body — it gave complainants and courts a measurable standard to test content against.
Inaccessible documents already drive complaints today — through the Department of Justice, and for schools and universities through the Department of Education's Office for Civil Rights. After your compliance date, disputes reduce to a technical question: does the file conform to WCAG 2.1 AA or fall under an exception? A verification report for every published file is the practical answer.
The work
What should your entity do now?
Inventory your public documents first — most entities find the backlog is far larger than the web team assumed, and documents in active use are the ones with no exception. Then classify, prioritize and remediate them to WCAG 2.1 AA before your compliance date, and fix your publishing workflow so new files go out accessible.
- Inventory: enumerate every PDF and Office document on your public domains, including files uploaded years ago. Scan your site free — no account, a few minutes.
- Prioritize: documents currently used to apply for or access services come first — they have no exemption. How risk ranking works.
- Remediate and verify: bring files to WCAG 2.1 AA and PDF/UA, and keep a verification report for each one. Bulk remediation · What a verification report contains.
- Fix the pipeline: make accessibility a publishing gate so the backlog never grows back. Continuous monitoring · Connections.
FAQ
ADA Title II document questions, answered
General information, not legal advice: which rule applies to you, and when, is a question for your counsel.
Does ADA Title II apply to public schools and universities?
Yes. Public school districts, public charter schools, community colleges and public universities are state or local government entities, so their websites, learning platforms and posted documents are covered. The final rule adopted no exception for password-protected course content: the only password-protected exception covers individualized documents about a specific person, property or account. Public-facing documents — enrollment forms, board packets, newsletters — are squarely covered.
Are scanned PDFs covered by the rule?
Yes. A scanned PDF posted on a public entity's website is web content like any other document. Because an image-only scan has no text layer, tags or reading order, it cannot meet WCAG 2.1 AA until you remediate it — OCR, tagging and verification — or replace it with an accessible version.
What does WCAG 2.1 Level AA mean for a document?
WCAG 2.1 AA is the Web Content Accessibility Guidelines, version 2.1, conformance level AA — the W3C standard the DOJ rule adopts. For your documents it translates to a tagged structure, logical reading order, a document title and language, alternative text, labeled form fields, header-tagged tables and adequate contrast.
What happens if an entity misses its compliance date?
The obligation still applies. The rule gives an individual entity no extension, waiver or grace period, so after the date the entity is out of conformance for the content the rule covers and exposed to complaints, DOJ enforcement and private lawsuits. The practical response is documented progress: a prioritized remediation plan and verified fixes, starting with the documents people use to reach your services.
Is content posted by vendors or third parties covered?
If a third party posts or maintains content for a public entity — a payment portal, an agenda-management platform, a document library — that content is covered as if the entity had posted it. Purely independent third-party content that an entity merely links to is generally not the entity's responsibility.
Can we just move old documents into an archive?
Only genuinely archival content qualifies for the archived-content exception. All four conditions must hold, including that the material is retained exclusively for reference, research or recordkeeping and sits in a dedicated area identified as archived. Moving a document people still use into an archive folder does not except it — and a document posted before your compliance date may already be excepted as a preexisting document, without moving it anywhere, unless people currently use it to reach a service.
Sources
Every regulatory claim on this page is cited to one of these primary sources.
- Federal Register, April 20, 2026 — Interim final rule: Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (91 FR 20902). This rule sets both compliance dates.
- eCFR — 28 CFR 35.200, the web and mobile accessibility requirements as currently in force
- US Department of Justice — Fact sheet: Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments (ADA.gov, 2024)
- Federal Register, April 24, 2024 — Final rule: Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (89 FR 31320). Creates the obligation and sets WCAG 2.1 AA; the compliance dates printed in it were later extended by one year.
- W3C — Web Content Accessibility Guidelines (WCAG) 2.1
- ADA.gov — US Department of Justice ADA information and technical assistance
Changelog
- Exception table and decision path added; entity-type guides, site scanner and product pages linked; FAQ on password-protected content corrected; Article schema and breadcrumb completed.
- Initial publication.
Reviewed quarterly, and whenever a cited source changes. Next review: December 18, 2026.