The ADA Title II Web Deadline: Every Date, and Which One Is Yours

If you run digital services for a city, county, state agency, school district, or special district, you have a fixed date by which your website, your mobile apps, and the documents you publish have to meet a specific technical standard. Most of the content you will find about that date is wrong, because the deadlines moved.

This post is the one place we keep the current dates. Every other accessibility article on this site links here rather than repeating them, so when they change again there is one thing to correct.

What are the current ADA Title II deadlines?

The Department of Justice’s 2024 rule under Title II of the Americans with Disabilities Act set the standard and the clock. An interim final rule in spring 2026 extended both compliance dates by roughly one year.

Who you are	Your deadline
A public entity serving a total population of 50,000 or more	April 26, 2027
A public entity serving under 50,000	April 26, 2028
Any special district government, regardless of population	April 26, 2028

The technical standard is WCAG 2.1 Level AA for both tiers. There is no small-entity exemption — a village, a township, and a single-purpose water district are all covered. Population changes the date, not the obligation.

Two things worth being precise about, because they are where the reassurance usually gets misread:

• The extension changed the dates, not the requirements. Everything substantive in the 2024 rule survived. Remediation work you have already scoped against WCAG 2.1 AA still counts.
• The deadlines are still ahead of you. They have not passed. What has changed is that the queue of everyone else needing the same work now compresses into the same window.

Which population number applies to me?

It is the total population your entity serves, not your staff headcount and not the number of people who visit your website. For a county, that is the county’s population. For a city, the city’s.

Special districts are treated separately and land on the later date whatever their size — a deliberate choice by DOJ, recognising that a fire protection district or a regional library system rarely has in-house web staff.

If you are genuinely on the line — a city hovering near 50,000 in the latest estimates — plan against the earlier date. The cost of being a year early is a year of not worrying about it.

What does WCAG 2.1 AA actually require of us?

WCAG is a technical standard, not a law. It is organised around four principles — content must be perceivable, operable, understandable, and robust — and Level AA is the practical bar regulators point at. If the distinction between the standard and the statutes is fuzzy, Section 508 vs ADA vs WCAG untangles the three.

In practice, meeting AA across a public-sector estate means:

• Every image carries meaningful alternative text, and decorative images are marked as decorative rather than described.
• Every function works from the keyboard alone, with a visible focus indicator.
• Colour contrast meets the ratios, including in charts and buttons.
• Video has accurate captions, and pre-recorded video needs audio description where visual information carries meaning.
• Forms have programmatic labels, and errors are announced rather than shown only in red.
• Documents you publish are tagged, with a correct reading order — which is where most agencies discover the real size of the job.
• The language of the page is declared, and any passage in another language is declared too.

That last one catches almost everyone who translates. If you publish a Spanish version of a form, the Spanish has to be marked as Spanish or a screen reader will read it aloud with English pronunciation rules — audible nonsense. We wrote about that specific failure in translated documents and WCAG language of parts.

Why the documents are the hard part

A website is a bounded project. You can audit it, scope it, fix it, and re-test it.

A document estate is not bounded. A mid-sized county typically has years of board minutes, budget books, permit applications, tax forms, public notices, and hearing packets published as PDFs — most produced by exporting from Word without a thought about tags. Every one of those is web content under the rule.

This is where the timeline gets real. Remediating a few thousand PDFs is not something that fits in the last quarter before a deadline, and it is not something an automated tool finishes on its own. Tools find problems; a person fixes reading order, table headers, and form fields.

The practical move is to triage rather than boil the ocean: start with what the public actually uses to transact — applications, notices, forms — and work backward through the archive.

What should we do in the next month?

A sequence that consistently works:

1. Fix the date you are working to. Write it on the project plan. Half the agencies we speak to are working to a deadline that no longer exists in either direction.
2. Inventory the documents. Not the pages — the documents. You cannot scope what you have not counted, and the count is usually a surprise.
3. Run a real audit, not just a scanner. Automated scans catch a meaningful slice and miss whole categories, including reading order and whether alt text is actually correct rather than merely present. How to run a website accessibility audit covers the difference.
4. Decide what is remediated and what is rebuilt. Some legacy templates are cheaper to replace than to patch.
5. Fix your publishing process at the same time. Otherwise you remediate the backlog while the backlog refills behind you.

Where Taika fits

We remediate documents and web content to WCAG 2.1 AA and Section 508, and we do it in more than one language — which matters if your public-facing materials exist in Spanish, Arabic, Vietnamese, or any of the languages your community actually speaks. Most accessibility vendors hand a translated file back untagged, and most translation vendors do not tag at all. Doing both in one pass is the whole point.

Start with document accessibility if the PDF estate is your problem, or ADA website accessibility if it is the site itself. If you are not yet sure which, an accessibility assessment will tell you the size of the job before you commit to it.

Ready to scope the work? Request a quote and tell us roughly how many documents and which languages you publish in — that is usually enough for us to come back with a realistic plan and sequence. If you would rather see where you stand first, run a file through the PDF accessibility checker and start from evidence.