The ADA Title II deadline, explained
If you work for a city, county, township, school district or special district in the United States, a federal rule now sets a date by which your website and your documents have to be usable by people with disabilities. Here is what it actually says.
What the rule requires
In April 2024 the Department of Justice finalized a rule under Title II of the Americans with Disabilities Act, amending 28 CFR Part 35. It sets one technical standard for state and local government digital content: WCAG 2.1, Level AA.
The part that catches most agencies by surprise is that this is not only about the website itself. Documents count. PDFs, Word files, spreadsheets and slide decks posted on your site are covered by the same standard as the pages around them. For most local governments, the documents are the larger share of the work — agendas, minutes, budgets, notices and forms accumulate for years.
Your date depends on your population
| Who you are | Compliance date |
|---|---|
| State governments, and local governments serving 50,000 people or more | April 26, 2027 |
| Local governments serving fewer than 50,000 people | April 26, 2028 |
| Special district governments, regardless of population | April 26, 2028 |
Those dates reflect a one-year extension the Department issued in April 2026. The technical standard did not change — only the calendar did.
Population means the people you serve, not your staff
A public library district serving a metro area of 300,000 is in the first group even if it has nine employees. A city of 12,000 is in the second group even if it has a large budget. If you are unsure which applies, the Census figure for the jurisdiction you serve is the number to use.
What is exempt — and the trap inside it
The rule does not require you to go back and fix everything ever posted. There are specific exceptions, and understanding them is the difference between a manageable project and an impossible one:
- Archived content — material kept only for reference, research or recordkeeping, that is not altered after the compliance date and is clearly identified as archived.
- Pre-existing electronic documents — PDFs, Word files and spreadsheets that were already on your site before your compliance date.
- Third-party content you do not post or control.
- Individualized password-protected documents, such as a specific resident's utility statement.
- Archived social media posts published before the compliance date.
The exception for old documents has a hole in it, and it is the important part
Pre-existing documents are exempt unless they are currently used to apply for, access, or participate in a service, program or activity.
In plain terms: a form is never exempt. A building permit application, a business license renewal, a records request, a park shelter reservation, a tax exemption claim — if a resident uses it to get something from you, it has to be accessible, no matter how long it has been sitting on your website.
This cuts both ways, and mostly in your favor. Most of a typical agency's document backlog is old minutes and notices, which are exempt. The work is much smaller than the file count suggests — but the forms in there are not optional.
What happens after your date
Everything you publish from your compliance date onward has to meet the standard. There is no grandfathering going forward. For a small city that posts twenty to fifty documents a month — agendas, minutes, notices, newsletters — that is the part that never ends, and it is what agencies most often fail to plan for. Fixing the backlog is a project. Staying compliant is a process.
Enforcement, realistically
Title II is enforced two ways: by complaint to the Department of Justice's Civil Rights Division, and by private lawsuit. Individuals have been able to sue under the ADA since 1990 — the new rule did not create that right, it clarified the standard a court would measure you against.
Some states are already past their deadline
Colorado is the clearest case. Under HB21-1110 and HB24-1454, state and local government digital content — including documents — had to be accessible as of July 1, 2025. There is no federal extension that applies: it is state law.
It also carries statutory damages of $3,500 per violation, payable to the person who sues, and it is enforced through private civil action rather than a state agency. If you are a Colorado entity, the federal 2027 and 2028 dates are not your deadline.
Where most agencies actually stand
The Department's own regulatory analysis scanned 28 government websites containing 43,502 PDFs and concluded that 95.2% of them would require some degree of remediation. That is not a scare number from a vendor; it is in the rule's published impact analysis.
Our own sampling of randomly selected municipal .gov sites found 97% of documents
failing at least one requirement — most commonly missing tag structure, which is the one that
makes a document unreadable to a screen reader rather than merely awkward.
If that sounds discouraging, it should not. It means your situation is normal, your peers are in the same position, and the realistic goal is not perfection by the deadline — it is knowing what you have, fixing what is required, and having a record of both.
See where your own documents stand
Enter your website and we'll inventory every PDF on it — how many fail, how many pages, and which ones are forms. Free, no signup.
Check your site