The ADA Title II extension isn't a reprieve. It's a countdown reset.
Summary
On April 20, 2026, the Department of Justice extended ADA Title II web accessibility compliance deadlines by one to two years for state and local government entities. The extension does not pause underlying accessibility obligations, and it does not extend the separate HHS Section 504 deadline that may apply to hospitals and nonprofits receiving federal funding. Organizations tracking a single calendar are exposed to what we call the two-deadline trap. The right response is to use the extension to systematize accessibility, not to defer it.
This article is not legal advice. Confirm which rules apply to your organization with qualified counsel.
Four days before the original compliance date, the DOJ reset the clock.
Per a summary from Jackson Lewis, state and local governments with populations over 50,000 now have until April 26, 2027 to comply with WCAG 2.1 Level AA under Title II. Smaller entities and special districts have until April 26, 2028.
If you run digital for a public entity, exhale. If the extension made you slow down, recalibrate. The deadlines moved, but the risk did not.
What actually changed, and what did not?
The DOJ pushed back the date that specific technical requirements become enforceable.
What did not change: the underlying ADA obligation to provide accessible programs and services. Title III public-accommodation risk for hospitals, providers, and nonprofits is unaffected. Demand letters and accessibility-related litigation continued straight through the extension announcement; they did not pause for it.
The compliance date is a deadline, not a start date. Organizations that wait will spend the extension period accumulating debt in templates, content, and vendor contracts, then attempt to remediate it in a sprint. That sprint is where the avoidable risk lives.
Why doesn’t the extension help hospitals and nonprofits?
The DOJ rule covers state and local government entities. It does not cover hospitals and nonprofits whose accessibility obligations come from a different source: federal financial assistance under Section 504 of the Rehabilitation Act.
Jackson Lewis notes that HHS has a separate Section 504 web accessibility compliance date, and as of this writing it has not been extended. Until HHS acts, plan as if it holds.
If your organization receives HHS funding, operates patient portals, runs scheduling or billing flows, accepts donations online, or hosts learning and event platforms, your timeline is likely shorter than the DOJ headline suggests. Title III public-accommodation exposure runs alongside it.
What is the two-deadline trap?
The two-deadline trap is the assumption that a single, well-publicized accessibility deadline is the only one that applies to your organization.
It happens when leadership tracks the DOJ Title II extension and treats it as the program’s primary clock, while a separate Section 504 or Title III obligation governs the actual exposure. The result is a roadmap pegged to the wrong date and a remediation budget that arrives late.
Avoiding it requires confirming, in writing and with counsel, which rules apply, which deadlines govern, and which user-facing services fall inside each scope.
What does day-one compliance actually look like?
Day-one compliance is the day your organization can demonstrate that new content is published accessibly, high-impact user flows work with assistive technology, vendors are managed as part of your posture, and governance is in place.
In our experience working with regulated organizations, the failure mode is rarely the homepage. It is the publishing system that keeps creating new accessibility debt — new pages, new PDFs, new embedded forms, new third-party widgets — faster than remediation can clear it. A defensible program stops the inflow before it works down the backlog.
That means accessibility moves upstream into design system components, CMS templates, content briefs, QA gates, and vendor intake. “Archived content” stops being a folder name and becomes a governance decision with rules. Procurement language changes so the next contract renewal does not lock in another year of vendor risk.
Will an accessibility overlay protect you?
No. Overlays can adjust some visual and interaction settings for some users, but they do not remediate the underlying barriers in your templates, components, content, or third-party tools. The Overlay Fact Sheet, signed by hundreds of accessibility practitioners and organizations, documents the consensus position.
If a widget is your strategy, assume you still need code-level fixes in templates, manual testing with assistive technology, content authoring training, and a third-party tool plan. The widget is not a substitute for any of those, and a number of overlay vendors have themselves been named in accessibility lawsuits.
What should accessibility leaders do this week?
Five actions, in order.
- Confirm which rules apply, and which deadline governs. Title II, Section 504, Title III, or more than one. If there is uncertainty, this is a counsel question, not an internal one.
- Name a single accessibility owner. Not a committee, but one person responsible for coordinating across IT, content, legal, and procurement. Accountability is the program.
- Test your top five user-critical flows manually. Forms, authentication, scheduling, payments, donations, patient portal — whatever blocks access to your primary services. Manual keyboard-only and screen reader software spot checks find what automated scanners miss.
- Inventory third-party tools and audit their contracts. Where contracts are silent on accessibility, flag them as priority renewals. Your compliance posture runs through every embedded vendor whether the contract says so or not.
- Write a 90-day plan and share it with leadership. Specific, resourced, and tracked beats comprehensive and aspirational every time.
The extension is not a year off. It is a year to put a defensible program in place before the rules apply more explicitly than they already do. Use it wisely.
