ADA Title II document requirements explained

Title II of the Americans with Disabilities Act now carries a specific technical standard for the documents governments publish online. This guide explains, in plain language, what the DOJ's 2024 web accessibility rule requires for PDFs and other document formats, who must comply and by when, and which exceptions actually apply.

What does the ADA Title II web rule require for documents?

The rule requires state and local governments to make web content — explicitly including PDFs, Word documents, presentations and spreadsheets — conform to WCAG 2.1 Level AA. It was published in the Federal Register on April 24, 2024 as subpart H of 28 CFR Part 35, and it is enforceable regulation, not guidance (final rule, 89 FR 31320). The 2024 rule still supplies the standard and the scope; only its compliance dates have since changed.

• Scope: content a public entity provides or makes available on the web
• Documents named in the rule's definition of "conventional electronic documents"
• WCAG 2.1 AA as the enforceable technical standard
• Relationship to the pre-existing general Title II obligations

Who is covered by the rule?

Every state and local government entity is covered: cities, counties, school districts, public colleges and universities, courts, and special districts such as libraries, transit and water authorities. Contractors publishing on an entity's behalf are covered through the entity. Federal agencies are not — they follow Section 508 instead.

• State and local governments, departments and instrumentalities
• Public schools, districts, and public higher education
• Special district governments (libraries, transit, water, parks, housing)
• Vendors and contractors acting for a public entity

When must documents comply?

Entities with a total population of 50,000 or more must comply by April 26, 2027. Entities under 50,000 and every special district government must comply by April 26, 2028. Both dates are set by the DOJ's interim final rule of April 20, 2026, which amended 28 CFR 35.200(b) to extend each cohort by one year from the dates originally printed in the 2024 final rule (interim final rule, 91 FR 20902; 28 CFR 35.200, eCFR). Population comes from Census figures; state agencies and public universities take the whole state's population, which puts them in the earlier cohort.

• The two dates and how the cohorts are drawn
• How population is determined (Census, service population edge cases)
• Special districts always in the 2028 cohort regardless of size
• What "compliance" means on the date: new and existing covered content

What technical standard do documents have to meet?

WCAG 2.1 Level AA is the standard the rule names. For documents that means, in practice: a correct tag structure and reading order, a document title and language, alternative text for images, labeled form fields, marked table headers, and sufficient contrast. PDF/UA is not required, but it is the cleanest way to satisfy WCAG for PDFs.

• WCAG 2.1 AA success criteria that matter most for documents
• How PDF/UA (ISO 14289) relates to WCAG for PDFs
• Word, PowerPoint and Excel: same criteria, different mechanics
• Why "passes a checker" is the floor, not the ceiling

Which documents are excepted?

Two exceptions do most of the work: archived web content and preexisting conventional electronic documents. Both are narrow. In the rule's own words, the second one covers Conventional electronic documents that are available as part of a public entity's web content or mobile apps before the date the public entity is required to comply with this subpart, unless such documents are currently used to apply for, gain access to, or participate in the public entity's services, programs, or activities (28 CFR 35.201(b)). The moment someone needs a document for one of those things, the exception falls away.

• The archived-content exception's four cumulative conditions
• Preexisting documents: which files count as available before the compliance date, and what ends the exception
• Third-party content and password-protected individualized documents
• Why relying on exceptions is a risk decision, not a filing cabinet

What should a compliance program look like?

Start with an inventory: you cannot remediate what you have not found. Then triage by usage and risk, fix the documents residents actually need first, set an accessible-by-default publishing workflow, and keep evidence. The deadline is a date for the program to be working, not a date to start.

• Inventory and classification of the document backlog
• Triage: active-use documents, high-traffic, forms, then the long tail
• Fix the pipeline: templates and workflows so new documents publish accessible
• Verification, records and an accessibility statement with a feedback channel

Where does DocoMatic fit?

DocoMatic automates the inventory, remediation and verification loop for exactly this obligation: it finds the documents on your domains, remediates PDFs to WCAG 2.1 AA / PDF/UA, verifies every file with machine checks plus human review where it matters, and produces the evidence records a coordinator can hand to counsel.

• Automated discovery against your public domains
• Remediation levels and verification thresholds
• Evidence and reporting for audits and grievances