Ask five city and county IT directors which ADA Title II deadline applies to their agency, and you will likely get five different answers — several of them wrong. Not because anyone is careless. Because the rule that decides it isn't obvious until you go looking for it, and most people never do until a compliance memo lands on their desk with a date attached and no explanation of how that date was chosen.
That single number — the population your entity serves — is the entire test. Get it wrong, and you either scramble in a panic you didn't need, or you relax into a deadline that was never yours to claim.
The Rule in One Paragraph
Under the Department of Justice's Interim Final Rule (Federal Register 2026-07663, effective April 20, 2026), every public entity covered by ADA Title II — state and local governments and the agencies that act on their behalf — has to bring its web content and mobile applications up to WCAG 2.1 Level AA. That part isn't in question. What splits agencies into two different timelines is a single factual question: how large is the population your entity serves?
Public entities serving 50,000 or more people must reach conformance by April 26, 2027. Public entities serving fewer than 50,000 people get an extra year, until April 26, 2028. And — this is the detail that trips people up — any special district government must comply by April 26, 2028, no matter how many people it serves. A special district covering a metro area of two million residents is still in the 2028 bucket, purely by virtue of what kind of entity it is.
The Stat: Public entities serving a population of 50,000 or more must comply with WCAG 2.1 AA by April 26, 2027, while entities serving fewer than 50,000 people — and any special district regardless of population — have until April 26, 2028. (Source: DOJ Interim Final Rule, Federal Register 2026-07663)
Notice what the chart is actually showing: the taller bar isn't "more compliant" or "higher priority" — it's simply farther out on the calendar. The shorter bar, sitting closer to today, is the one with less runway.
Why "Population Served" Isn't Always Obvious
The population test sounds simple until you try to apply it to your own organization. A few situations that generate real confusion:
State agencies. A state department of motor vehicles or a state unemployment office serves the entire state's population — which puts nearly every state-level agency in the 2027 bucket, regardless of how small its own staff or budget is. Size of the agency isn't the test. Size of the population it serves is.
County and city agencies in larger jurisdictions. A parks department in a county of 40,000 residents may fall under the 2028 timeline, while a parks department in a county of 400,000 falls under 2027 — even if the two departments look nearly identical in staffing and website complexity.
Third-party-operated services. The rule extends to some services performed on behalf of a public entity by a third party — a contracted benefits portal or an outsourced permitting system doesn't get a free pass just because a vendor runs it. If the underlying entity serves 50,000 or more people, the service performed on its behalf is generally pulled into that same population bucket.
Special districts, full stop. This is the carve-out worth memorizing: transit authorities, water districts, fire districts, and similar special-purpose governments are placed in the 2028 bucket categorically. Population is irrelevant for this entity type. A transit authority moving a million riders a year and a rural fire district serving a few thousand residents land on the identical April 26, 2028 date, for the identical reason — entity type, not population.
The Quick Checklist
Before assuming which deadline applies, walk through this in order:
| Step | Question | If yes |
|---|---|---|
| 1 | Is your entity a special district government (transit, water, fire, utility, etc.)? | You're in the 2028 bucket — population doesn't matter. Stop here. |
| 2 | If not a special district: does your entity serve 50,000 or more people? | You're in the 2027 bucket. |
| 3 | Does your entity serve fewer than 50,000 people? | You're in the 2028 bucket. |
| 4 | Do you rely on a third party to operate a service on your behalf? | That service generally inherits your entity's bucket — confirm it's in scope too. |
| 5 | Regardless of bucket: is your target WCAG 2.1 Level AA, applied to web and mobile? | Yes — the technical standard doesn't change between buckets, only the deadline does. |
That last row matters as much as the date itself. Neither bucket gets a lower bar to clear — both are held to the same WCAG 2.1 AA standard for web content and mobile applications. The only thing the population test changes is how much runway you have to get there.
Why the Extra Year Isn't as Much Cushion as It Sounds
If your entity lands in the 2028 bucket, it's tempting to treat that as "we have time." In practice, a lot of that runway disappears fast. Remediation work — auditing every template, fixing color contrast, rebuilding inaccessible forms and PDFs, retraining content teams — takes months even for a modestly sized site, and accessibility problems tend to be more widespread than anyone expects going in.
That expectation isn't a guess. Independent, large-scale evaluations of the web keep finding the same thing: roughly 95.9% of home pages checked in the WebAIM Million have at least one detectable WCAG 2 failure. Most agency websites — built over years, by different vendors, with different content management habits — are not the exception to that pattern. And the population affected by getting this right is enormous: roughly 1 in 4 U.S. adults live with some form of disability, according to the CDC, so accessibility gaps aren't an edge case in your traffic — they're a routine part of it.
Confirm Your Bucket, Then Act on It
The population test is a factual question with a factual answer, but it's not always the answer people assume on first guess. A state agency assuming it's "too small" to matter, or a special district assuming its size buys extra time either way, are two of the most common wrong turns. Before you build a remediation timeline, budget request, or vendor contract around a deadline, confirm — with your actual population-served figure and entity type — which bucket you're really in.
Whichever bucket applies, the work is the same: an honest, criteria-by-criteria look at where your web and mobile properties currently stand against WCAG 2.1 AA. That's exactly what a full audit gives you before you commit resources to a plan. If you haven't confirmed your deadline or don't yet know how far your current site is from WCAG 2.1 AA, get a full accessibility audit and start your remediation plan with real numbers instead of assumptions.