Skip to main content
Back to all posts

ADA Title II Deadline Extended: What It Does Not Excuse

Benjamin Morton

Four days. That's how much warning state and local governments got. On 20 April 2026, the Department of Justice published an interim final rule extending the ADA Title II web accessibility compliance deadline by a year, with the original date, 24 April 2026, four days away (Federal Register, 2026).

If you build for a city, a county, a school district, or a public university, you probably read the headline and exhaled. Read on before you re-plan the roadmap. The extension is real, but it's narrower than the headline suggests, it's being challenged in federal court, and for a large class of small, HHS-funded public bodies with 15 or more employees, Title II was never the deadline that actually bound them. This piece is about what the delay really bought you. It sits alongside our web accessibility compliance guide.

TL;DR: DOJ pushed Title II web compliance to 26 April 2027 (population 50,000+) and 26 April 2028 (under 50,000). HHS separately pushed its Section 504 deadline to 11 May 2027 for recipients with 15 or more employees. Both rules moved by a year, which preserved a gap already baked into the 2024 rules: a small public entity taking HHS money and employing 15 or more people faces Section 504 eleven months before its Title II date. The relief everyone reported was measured against the wrong deadline. The National Federation of the Blind is suing to vacate both extensions and reinstate the deadlines the 2024 rules originally set. Meanwhile government home pages still average 42.4 detectable accessibility errors each (WebAIM, 2026).

What Changed in the ADA Title II Compliance Deadline

Two rules moved, not one, and they're easy to conflate. DOJ published its Title II extension on 20 April 2026, effective immediately, four days before the deadline it was extending. HHS then signed its parallel Section 504 extension on 7 May 2026 and published it on 11 May, which was the day the old Section 504 deadline actually fell due (Federal Register, 2026). One agency beat its own deadline by four days; the other landed on the day itself.

Each pushed its dates out by a year, and both keep WCAG 2.1 Level AA as the technical standard. Neither changed what conformance means, only when it's due.

Rule

Who

Was

Now

ADA Title II (DOJ)

Public entities, population 50,000+

24 Apr 2026

26 Apr 2027

ADA Title II (DOJ)

Public entities under 50,000, special districts

26 Apr 2027

26 Apr 2028

Section 504 (HHS)

HHS-funded recipients, 15+ employees

11 May 2026

11 May 2027

Section 504 (HHS)

HHS-funded recipients, under 15 employees

10 May 2027

10 May 2028

Sources: Federal Register 2026-07663 (DOJ) and Federal Register 2026-09266 (HHS), 2026.

Reaction split along predictable lines. The National Association of Counties, which had lobbied for exactly this, called it "a significant win for counties" (NACo, 2026). The American Association of People with Disabilities called it "a profound disappointment and a serious setback", and its President and CEO, Maria Town, pointed at the timing: "Delaying the compliance timeline only four days before the original deadline does not support state and local governments who are working to implement the rule. It creates chaos and confusion for those entities working towards compliance" (AAPD, 2026).

The Deadline Everyone Reported Is the Wrong One

Section 504 lands eleven months before Title II for small HHS-funded public entities with 15 or more employees. That gap isn't new, and that's the part worth sitting with. Both rules moved by a year, so the extension preserved an ordering that was already baked into the 2024 rules rather than creating it.

Take a public body with a population under 50,000 that also receives HHS funding and has 15 or more employees. A county health department. A public hospital district. A school district billing Medicaid for school health services. Its Title II deadline is now 26 April 2028. Its Section 504 deadline is 11 May 2027.

For that entity, Title II was never the binding constraint, before the extension or after it. The coverage was all about DOJ, so the relief got measured against a date that was never the one to beat. Read the Title II headline, stand down, and you walk past a live federal deadline nearly a year closer.

The employee count is what swings it, so check yours before you file this away. Drop below 15 employees and the ordering flips: Section 504 moves out to 10 May 2028, two weeks after the same entity's 26 April 2028 Title II date. Above 15 employees, Section 504 rings first by eleven months. Below it, Title II rings first by a fortnight.

Citation capsule: The DOJ and HHS extensions each moved their deadlines by a year, preserving an ordering already present in the 2024 rules. A public entity under 50,000 population that also receives HHS financial assistance and employs 15 or more people faces a Section 504 compliance date of 11 May 2027 (Federal Register, 2026) but a Title II date of 26 April 2028 (Federal Register, 2026). For these entities the Section 504 clock rings eleven months first, so the widely-reported Title II relief is not their operative deadline. Below 15 employees the order reverses: Title II falls due 26 April 2028 and Section 504 on 10 May 2028.

For large entities the two dates are effectively the same anyway: Title II on 26 April 2027, Section 504 on 11 May 2027, fifteen days apart. A well-funded city gets no meaningful reprieve on one that it doesn't also get on the other.

The Extension Might Not Survive

The rule you'd be planning against is under active legal attack. On 21 May 2026, the National Federation of the Blind sued both DOJ and HHS in the US District Court for the District of Maryland, challenging both interim final rules together (NFB, 2026).

Look at what the suit asks for. It asks the court to declare the extensions unlawful, vacate both rules, and order the agencies to enforce the deadlines originally set by the 2024 rules (Seyfarth Shaw, 2026). The core claim is procedural: that issuing an interim final rule skipped the notice-and-comment process the Administrative Procedure Act requires, and that the agencies acted arbitrarily.

A win would land differently depending on your size, and the distinction matters. Large entities (population 50,000+) and HHS recipients with 15 or more employees had original dates of 24 April and 11 May 2026. Both are already behind us, so a vacatur would leave those entities immediately exposed to a deadline that, legally speaking, never moved. Smaller bodies would snap back to a date that hasn't arrived yet: 26 April 2027 under Title II, or 10 May 2027 for HHS recipients under 15 employees. Still ahead of them, but a full year tighter than what they're planning against today.

No ruling has come down as of July 2026, so this is a risk to price in rather than a certainty. Betting a two-year roadmap on the survival of a rule that's being actively litigated is still a strange thing to do on purpose.

In fairness, the pressure runs both ways. DOJ has announced plans in the Federal Register to issue a new proposed rulemaking exploring ways to lower the cost of compliance with the 2024 rule (NACo, 2026), so more relief may genuinely be coming. The delay is real, narrow, contested, and unevenly distributed all at once.

What the Title II Extension Does Not Touch

The floor underneath all of this never moved, and DOJ says so itself. Its own guidance, published after the extension, still reads: "The ADA requires that state and local governments must provide individuals with disabilities with effective communication, reasonable modifications, and an equal opportunity to participate in or benefit from their services, programs, and activities" (ADA.gov, 2026). The same page is explicit that even where an exception applies to some content, "the government must still satisfy its other obligations under the ADA" to provide exactly those things.

Those duties are not new, and they're not theoretical. They supported web accessibility enforcement for more than a decade before any technical standard existed in regulation:

  • Louisiana Tech University, 2013. DOJ settled over an inaccessible online learning product that locked out a blind student. The university was required to bring learning technology, web pages, and course content into conformance with WCAG 2.0 Level AA, train staff, and pay $23,543 in damages (US Department of Justice, 2013).
  • Miami University, 2016. A consent decree required web content and learning management systems to conform to WCAG 2.0 Level AA (US Department of Justice, 2016).

Those settlements predate the 2024 rule by eleven and eight years respectively. DOJ extracted WCAG conformance from public universities with no WCAG deadline on the books at all, using nothing but Title II's general duties. Those are precisely the duties the 2026 extension leaves untouched. "No deadline" has never meant "no obligation", and that's a matter of record rather than rhetoric.

Citation capsule: DOJ imposed WCAG 2.0 Level AA conformance on public universities years before any web accessibility regulation existed, settling with Louisiana Tech University in 2013 (US Department of Justice) and entering a consent decree with Miami University in 2016 (US Department of Justice). Both rested on Title II's effective-communication and nondiscrimination duties, which the 2026 compliance-date extension does not alter.

One honest caveat. We could not find a documented DOJ Title II web enforcement action against a public entity during 2025 or 2026. The legal duty is well evidenced by the precedent above. A current wave of Title II litigation is not something the public record supports, and we're not going to imply one. Title III filings against private businesses are a separate and much noisier story, which we cover in ADA website lawsuits.

How Bad Are Government Sites, Actually?

Bad, and getting worse, though not as bad as everywhere else. WebAIM's 2026 scan of a million home pages found 95.9% had detected WCAG failures, up from 94.8% in 2025 and reversing the gradual improvement of recent years. Errors per page rose 10.1%, to an average of 56.1 (WebAIM Million, 2026).

Government is among the strongest of the sectors WebAIM breaks out, averaging 42.4 detectable errors per home page, fewer than Education on 48.9 and well below the 56.1 overall average. Before anyone celebrates, note what "strongest" means here: a sector doing better than the web at large still ships more than forty machine-detectable accessibility errors on its front door.

Only 4.1% of pages in the study had no detectable errors at all, and WebAIM adds that because only automatically detectable failures were counted, "the rate of full WCAG 2 A/AA conformance was certainly lower than 4.1%" (WebAIM Million, 2026). That's the baseline the extra twelve months has to be measured against.

What to Do With the Extra Year

Use it, because the six failure types causing 96% of all detected errors are the cheap ones (WebAIM Million, 2026). Low-contrast text, missing alt text, missing form labels, empty links, empty buttons, and a missing document language. All six are machine-detectable, and all six map directly onto axe-core rules.

1. Work out which deadline actually binds you. If you take HHS money, check both your population band and your employee count. Under 50,000 with 15 or more employees, your real date is 11 May 2027, not April 2028. Over 50,000, Title II still lands first, on 26 April 2027. Getting this wrong is the most expensive mistake available right now.

2. Scan before you plan. You cannot scope remediation you haven't measured. Start with your highest-traffic templates: home, service pages, forms, payment flows, and anything a resident has no alternative route to.

3. Fix the six, then gate them. Our guide to fixing common WCAG violations has the code, and the GitHub Actions guide wires axe-core into CI so new violations fail the build. A one-off remediation with no gate decays back to where it started.

4. Target WCAG 2.2 AA, not 2.1. The rules mandate 2.1 AA, but 2.2 is largely additive, so building to 2.2 satisfies the mandate and insulates you from the next revision. Our WCAG 2.2 checklist covers the criteria.

5. Don't reach for an overlay. A widget doesn't repair the DOM underneath it, and the barriers stay exactly where they were. We've covered why overlays fail in detail.

If you're the vendor, not the agency, read your contract before you relax. The agency's regulatory deadline moved; your contractual obligations almost certainly did not. Accessibility conformance requirements, VPAT or ACR commitments, and flow-down clauses sit in the contract, and they're enforceable on their own terms whatever DOJ does with the rule. A procurement that specified WCAG 2.1 AA as a deliverable still specifies it today.

Even NACo, which lobbied hard for the delay and called it "a significant win for counties", closed its own announcement with this: "Counties remain committed to making local digital services accessible for all residents" (NACo, 2026).

Frequently Asked Questions

What is the new ADA Title II web accessibility deadline?

Public entities with a population of 50,000 or more now have until 26 April 2027. Entities under 50,000, and all special district governments, have until 26 April 2028 (Federal Register, 2026). The technical standard remains WCAG 2.1 Level AA. The extension changed the dates, not the requirements.

Was the Section 504 deadline extended too?

Yes, but separately and to different dates. HHS extended Section 504 web accessibility compliance for recipients of its financial assistance to 11 May 2027 (15 or more employees) and 10 May 2028 (fewer than 15) (Federal Register, 2026). For a small HHS-funded public entity with 15 or more employees, that falls eleven months before its Title II date. Below 15 employees, Title II comes first instead.

Could the extension be reversed?

Possibly. The National Federation of the Blind sued DOJ and HHS in the District of Maryland on 21 May 2026, asking the court to vacate both interim final rules and reinstate the deadlines set by the 2024 rules (NFB, 2026). No ruling has issued. A vacatur would expose large entities immediately, since their original dates have already passed, and would pull smaller bodies back to 26 April 2027 under Title II (or 10 May 2027 for small HHS recipients).

Does the delay mean my agency has no accessibility obligations until 2027?

No. Title II's effective-communication and nondiscrimination duties apply now and are untouched by the extension, as DOJ's own guidance states (ADA.gov, 2026). DOJ enforced WCAG conformance against Louisiana Tech in 2013 and Miami University in 2016, years before any technical standard existed in regulation.

How accessible are government websites today?

Not very. Government home pages average 42.4 detectable accessibility errors each, among the strongest of the sectors WebAIM breaks out in its 2026 scan of one million pages, against an overall average of 56.1 and a 95.9% failure rate (WebAIM Million, 2026). Because only automatically detectable failures were counted, WebAIM notes true conformance is "certainly lower than 4.1%".

The Bottom Line

The ADA Title II compliance deadline moved. Your obligations didn't. DOJ bought public entities twelve months on the WCAG 2.1 AA mandate, then said in the same breath that effective communication, reasonable modifications, and equal opportunity still apply today (ADA.gov, 2026).

Three things make the extension worth less than it looks. Small entities taking HHS money and employing 15 or more people face Section 504 eleven months earlier than Title II, so the relief everyone reported was never their binding date. The NFB is asking a federal court to vacate both extensions and reinstate the deadlines the 2024 rules originally set. And government sites still average 42.4 detectable errors on the home page, in a year when the web got worse rather than better (WebAIM Million, 2026).

So spend the year rather than banking it. Work out which of the two deadlines actually binds you, run a scan, fix the six failures behind 96% of errors using our common WCAG violations guide, and gate them in CI with the GitHub Actions setup so they don't come back.

Sources

PreviousADA Website Lawsuits: The Statistics Developers Need in 2026
NextWeb Accessibility Statistics 2026: The Numbers That Hold Up