If your agency's compliance plan for the ADA Title II web accessibility rule was "we'll get to it before April 2026," the Department of Justice just handed you a gift you didn't ask for and probably don't deserve: more time. On April 20, 2026, DOJ published an Interim Final Rule in the Federal Register (document 2026-07663) extending the compliance dates for state and local government entities. The original April 26, 2026 deadline is gone. In its place are two new dates, staggered by population size.
That sounds like relief. For agencies that spent the last two years building an accessibility program, it is relief — breathing room to finish testing, close remediation tickets, and validate vendor claims before an enforcement clock starts ticking. For every agency that spent the last two years hoping the deadline would move, it's something else entirely: a second chance to make the exact same mistake, on a longer fuse.
What the Interim Final Rule Actually Changed
The rule DOJ finalized under Title II of the ADA in 2024 required state and local government entities to make their web content and mobile applications conform to WCAG 2.1 Level AA. That requirement itself has not changed. What changed on April 20, 2026 is only the compliance calendar:
- The original deadline — April 26, 2026, for all covered public entities — no longer applies.
- State and local government entities serving a population of 50,000 or more now have until April 26, 2027.
- Public entities serving a population under 50,000, and any special district government regardless of population, now have until April 26, 2028.
That's the entire substantive change. DOJ didn't rewrite the technical standard, didn't narrow the scope of what counts as "web content," and didn't exempt any category of entity from eventual compliance. It moved the finish line further out for two groups and left everyone still running the same race.
The Stat: DOJ's Interim Final Rule (Federal Register document 2026-07663), effective April 20, 2026, extended the ADA Title II web and mobile app accessibility compliance date from April 26, 2026 to April 26, 2027 for public entities serving 50,000 or more people, and to April 26, 2028 for entities serving fewer than 50,000 people and all special district governments. (Source: U.S. Department of Justice, Federal Register)
The New Deadlines, By Entity Size
The staggered structure matters because it determines exactly how much runway your agency has left — and runway is the one resource nobody gets more of by waiting.
| Entity Type | Original Deadline | New Deadline | Extension |
|---|---|---|---|
| All covered public entities (as originally written) | April 26, 2026 | — | Superseded |
| State/local government, population 50,000+ | April 26, 2026 | April 26, 2027 | +1 year |
| State/local government, population under 50,000 | April 26, 2026 | April 26, 2028 | +2 years |
| Special district governments (any population) | April 26, 2026 | April 26, 2028 | +2 years |
Notice what the table doesn't contain: a "no deadline" row. Every category of covered entity still has a hard date on the calendar. The rule didn't create an off-ramp — it created two different lengths of on-ramp.
Why an Extension Isn't the Same as Relief
It's worth being precise about what DOJ actually granted here, because "we have more time" and "we have less to do" are not the same sentence, and treating them as interchangeable is how agencies end up scrambling in March 2027 or March 2028 instead of sitting comfortably ahead of the date.
The underlying accessibility problem the rule exists to solve hasn't gotten smaller while the deadline moved. Independent of any single agency's specific pages, the general state of the web remains difficult for people using assistive technology. The WebAIM Million study has repeatedly found that roughly 95.9% of home pages have at least one detectable WCAG 2 failure — and that figure comes from scanning the open web broadly, not some worst-case subset. Government websites are not exempt from that baseline reality just because they're public-sector.
The population affected by inaccessible public services is also not small or hypothetical. The CDC estimates that roughly 1 in 4 U.S. adults live with some form of disability — a population that includes residents applying for permits, paying utility bills, requesting public records, and using 911 or emergency alert systems through the exact web and mobile channels this rule covers. Color-dependent interfaces compound the problem for an even broader slice of users: the World Health Organization estimates that approximately 8.3% of men and 0.5% of women have some form of color vision deficiency, which is one of the most common — and most commonly ignored — accessibility failures in government dashboards, maps, and status indicators that rely on color alone to convey meaning.
None of those numbers changed on April 20, 2026. What changed is how long agencies have before noncompliance becomes something a resident, an advocacy group, or DOJ itself can point to on a specific calendar date.
The Technical Standard Did Not Move
This is the detail that gets lost in "deadline extended" headlines: WCAG 2.1 Level AA is still the required conformance target for both web content and mobile applications, unchanged by the Interim Final Rule. Agencies hoping the extension signaled a lighter technical bar, or a rewrite of scope, will find neither. The rule DOJ finalized originally is still the rule. The only variable that moved is the date by which a given entity, based on its population, must be able to demonstrate conformance.
That's a meaningful distinction for anyone budgeting remediation work. A vendor contract negotiated on the assumption that "the standard might get relaxed" is negotiated on a false premise. WCAG 2.1 AA — covering things like sufficient color contrast, keyboard operability, meaningful alt text, and correctly labeled form fields — is the fixed target regardless of which of the two new dates applies to your entity.
What to Do With the Extra Time, Concretely
The agencies that come out ahead on this extension will treat it the same way a well-run capital project treats a schedule change: as additional time for verification, not as a reason to restart planning. A practical sequence looks like this:
- Confirm your population classification now. Whether your entity falls above or below 50,000, or qualifies as a special district, determines which of the two new dates governs you — get that classification in writing rather than assuming it.
- Run a full conformance audit against WCAG 2.1 AA, not a spot-check of the homepage. Public entities typically operate dozens of subsites, portals, and third-party-embedded tools (permitting systems, payment processors, GIS map tools) that fall outside a simple homepage review but are squarely in scope.
- Prioritize by usage and legal exposure, not by ease of fix. High-traffic services — tax payment, benefits applications, public notices, emergency communications — carry the most risk if they remain inaccessible past the deadline.
- Get vendor commitments in writing, including specific WCAG 2.1 AA conformance language and remediation timelines, for any third-party platform your entity doesn't control directly.
- Re-test before the deadline, not at it. An audit conducted a year before your date is a planning document. An audit conducted the month of your date is a confession.
The Real Countdown
DOJ's extension bought state and local governments something genuinely valuable: one to two additional years to get this right instead of doing it under deadline panic. But an extension is only relief if it's used as one. Agencies that treat April 26, 2027 or April 26, 2028 the way they treated April 26, 2026 — as a distant date rather than a fixed one — will find themselves in the same position next year, just with less sympathy available and less runway remaining.
The agencies and vendors who come out ahead of this will be the ones who know exactly where they stand today, not the ones who find out in the final quarter before their deadline. If you want that clarity now, rather than guessing at your exposure, get a full accessibility audit and see precisely what WCAG 2.1 AA conformance requires for your specific web content and mobile applications before the countdown restarts on you.