What Changed on April 20, 2026
For two years, April 24, 2026 was the date on every government web team's calendar: the day the Department of Justice's ADA Title II rule would require large state and local government entities to meet WCAG 2.1 Level AA for their websites and mobile apps.
Then, on April 20, 2026 — four days before the deadline — the DOJ published an interim final rule extending the compliance dates by one year (Federal Register 2026-07663).
This article was originally published as a guide to the April 24 deadline. It has been fully updated to reflect the extension: the new dates, what stayed the same, the legal challenge already filed against the delay, and what the change does — and does not — mean depending on who you are.
The essential summary: the deadline moved. The rule did not. WCAG 2.1 AA remains the codified federal standard for public entities, the DOJ has stated it will enforce the rule at the new dates, and the extension itself is now being contested in federal court.
The New Compliance Dates
The interim final rule shifts both compliance tiers by one year:
| Covered entity | Original deadline | New deadline |
|----------------|-------------------|--------------|
| State/local government entities serving populations of 50,000+ | April 24, 2026 | April 26, 2027 |
| Entities under 50,000 and special district governments | April 26, 2027 | April 26, 2028 |
Everything else about the rule's coverage is unchanged. It still applies to all web content and mobile applications of Title II entities: state agencies, cities and counties, public school districts, public universities, courts, transit authorities, public hospitals, libraries, and special districts. The technical standard is still WCAG 2.1 Level AA. The narrow exceptions (archived content, certain pre-existing documents, some third-party content) are still narrow.
One important caveat before anyone relaxes: as explained below, a pending lawsuit asks the court to reinstate the original dates. Treating April 2027 as a comfortable, guaranteed horizon would be a mistake.
What Did Not Change
The extension is a change of dates, not of substance. Three things are worth stating plainly:
The standard is still WCAG 2.1 Level AA. The interim final rule did not touch the technical requirement. Public entities will be measured against the same 50 success criteria in 2027 that they would have been measured against in 2026. Work already done toward the standard retains its full value. (Our WCAG 2.1 AA checklist covers every criterion — and testing against WCAG 2.2 AA exceeds the federal requirement.)
The rule was not rescinded. The DOJ has stated it will apply the rule at the new dates. Separately, in October 2025 the DOJ announced a deregulatory re-examination of its Title II and Title III regulations; that review is ongoing and its outcome is unknown. Planning should be based on the rule as it stands: in force, with 2027/2028 deadlines.
Courts still have their benchmark. For years before the rule existed, courts used WCAG 2.1 AA as the de facto reference for what an accessible website means. The federal codification of that standard for public entities did not evaporate with the date change — plaintiffs' attorneys cite it in private litigation regardless of when government entities must comply.
The NFB Lawsuit: The Extension Is Being Challenged
On May 21, 2026, the National Federation of the Blind filed suit challenging the extension, arguing the DOJ violated the Administrative Procedure Act in the way it issued the delay, and asking the court to reinstate the original compliance dates.
The case is pending. No outcome should be assumed in either direction. But the practical implication for covered entities is real: if the challenge succeeds, the original dates — one of which has already passed — could be restored. An entity that shelved its accessibility program in April 2026 could find itself out of compliance retroactively, with no runway.
This is the strongest argument for treating the extension as scheduling relief rather than a reprieve: the new dates are one court ruling away from moving back.
What This Means for State and Local Governments
If you run digital services for a Title II entity, the extension changes your timeline, not your obligation. If your entity was not fully conformant in April 2026, that gap is now a one-year work plan — not a grace period to be spent elsewhere.
A realistic use of the year:
- Now: Inventory every public-facing web property, portal, app, and document repository. Run automated scans to establish a violation baseline.
- Next two quarters: Remediate the highest-impact barriers on citizen-facing services — forms, navigation, PDFs in active use, contrast and labeling failures.
- Ongoing: Put accessibility checks into content workflows and deployment pipelines so the April 2027 date arrives as a confirmation, not a scramble.
- Throughout: Document everything. If the NFB litigation restores earlier dates, a documented, in-progress program is a very different posture than a paused one.
Public education institutions and government agencies face the same standard on the same clock — and vendors who sell to them should expect WCAG conformance documentation to keep appearing in procurement requirements regardless of the federal dates.
What This Means for Private Businesses: Nothing Changed
This is the most misunderstood part of the entire story, so it deserves to be said clearly.
ADA Title II never applied to private businesses. It covers state and local governments. The April 2026 deadline — extended or not — was never a compliance date for your e-commerce store, restaurant, clinic, or SaaS product. There is no federal deadline, and no federally codified technical standard, for private-sector websites under ADA Title III. There never has been.
That is not good news, though. The private-sector risk does not come from a regulation with a date. It comes from private litigation, which is at record volume and rising: 3,117 federal website lawsuits in 2025 (up 27%, per Seyfarth), more than 5,000 across all courts (UsableNet), and a 2026 pace projecting roughly 6,176 cases (+20%, UsableNet midyear). 79% of 2026 targets are e-commerce businesses and 68% of defendants make less than $50 million in revenue. The full data is in our lawsuit statistics report.
Courts in these private cases use WCAG 2.1 AA as the de facto measuring stick — which means the practical to-do list for a private e-commerce business is the same as for a city government. The difference is that a city knows its deadline. A business finds out its "deadline" when the demand letter arrives.
So if you are a private business and you saw headlines that "the ADA deadline was extended": nothing about your risk profile improved in April 2026. The deadline moved. The lawsuits didn't.
State Laws Did Not Wait
The federal extension did not ripple down to the states:
- Colorado did not follow the federal delay. Under HB21-1110, accessibility requirements for Colorado public entities have been fully enforceable since July 1, 2025, with exposure of $3,500 per violation per person.
- California's Unruh Civil Rights Act provides a minimum of $4,000 in statutory damages per violation plus attorney's fees, and is regularly applied to websites.
- New York remains the most active jurisdiction in the country for web accessibility claims, powered by the NY Human Rights Law in state court.
- Illinois emerged in the first half of 2026 as the second-busiest jurisdiction nationally, with 508 filings (UsableNet).
An organization that calibrated its accessibility program to the federal Title II date alone was always looking at a fraction of the map.
The Healthcare Parallel: HHS Section 504
The Title II extension has a sibling in healthcare. In May 2026, HHS similarly delayed the web accessibility deadlines under its Section 504 rule — which requires WCAG 2.1 AA from healthcare providers receiving HHS funds, including Medicare and Medicaid participants — to May 11, 2027 (providers with 15+ employees) and May 10, 2028 (fewer than 15), per Federal Register 2026-09266. That delay is challenged in the same NFB litigation.
Unlike Title II, the HHS rule reaches deep into the private sector: medical practices, dental offices, clinics, and pharmacies. If that is you, see our dedicated guide to the HHS Section 504 web accessibility deadline and the healthcare accessibility overview.
What to Do With the Extra Year
Whether you are a covered public entity or a private business watching the standard consolidate around WCAG 2.1 AA, the rational response to the extension is the same: use the time, don't bank it.
1. Establish your baseline now. An automated scan identifies the machine-detectable WCAG 2.1 AA and 2.2 AA issues on your site in minutes — the same issues cited in complaints and demand letters.
2. Fix in priority order. Alt text, form labels, contrast, keyboard access: the violations most cited in litigation are also the most fixable.
3. Make it continuous. 46% of 2026 lawsuit defendants are repeat defendants (UsableNet). Sites drift out of conformance with every update; monitoring is what keeps a one-time effort from expiring.
4. Watch the NFB case. If the original dates are restored, entities with an active, documented program will be the ones that are fine.
Scan your website free to see exactly where you stand against WCAG 2.1 AA and 2.2 AA — whichever way the dates move next.
Tags
Share this article