The DOJ’s Interim Final Rule extends ADA Title II compliance deadlines by one year but does not change the underlying accessibility requirements, legal obligations, or enforcement risk.
On Friday afternoon, April 17, 2026, the U.S. Department of Justice filed an Interim Final Rule extending the compliance deadlines for the 2024 ADA Title II web and mobile application accessibility rule by one year.
It was signed April 16 by Acting Attorney General Todd Blanche. Posted for public inspection on the morning of the 17th. Scheduled for Federal Register publication Monday, April 20. It is effective immediately upon publication, with a 60-day post-publication comment window.
If you've been building toward the April 24, 2026 compliance date for the last eighteen months, this is the moment to pause, read this carefully, and then not slow down.
Here is what the IFR actually does, what it does not do, and what it means if you are responsible for a state, local, higher ed, utility, airport, or special district digital presence.
What Changed in the ADA Title II Deadline Extension
The IFR extends both compliance tiers in the 2024 final rule by exactly one year:
- State and local government entities with a total population of 50,000 or more: compliance date moves from April 24, 2026 to April 26, 2027.
- Public entities with a population under 50,000, and all special district governments (regardless of size): compliance date moves from April 26, 2027 to April 26, 2028.
That's the entire substantive change. One year. Both tiers.
What Did Not Change (And Why It Matters)
This is the part that matters, and it's also the part that's easiest to miss in the headlines.
The IFR explicitly leaves every other provision of the 2024 final rule intact.
- WCAG 2.1 Level AA remains the incorporated technical standard.
- Every provision describing how WCAG 2.1 applies to public entities' web content and mobile apps remains in force.
- The exceptions carved out in the 2024 final rule (archived content, preexisting conventional electronic documents, third-party content that is not posted by or on behalf of the entity, password-protected content in limited circumstances, and individualized content for specific people) are unchanged.
- The underlying Title II nondiscrimination obligation has existed since 1992. The 2024 rule codified what DOJ settlements have required since 2015. Neither moved.
- The private right of action is still in place. DOJ could not have eliminated it in this IFR even if it wanted to. Congress created that right by statute.
DOJ says this plainly in the IFR itself. Covered entities "have an ongoing obligation to ensure that their services, programs, and activities offered using web content and mobile apps are accessible to individuals with disabilities in accordance with their existing obligations under title II of the ADA."
Your lawsuit risk today is identical to your lawsuit risk on Thursday. The plaintiff's bar is not waiting on a federal deadline. More than 8,000 web accessibility cases were filed in 2025. They will not slow down in 2026.
Why the DOJ Extended the ADA Deadline
The IFR's stated reasoning is worth reading closely because it tells you where the next round of rulemaking is headed.
DOJ cites four categories of new information it received after the 2024 rule was finalized:
- Resource constraints that were underestimated. The Small Business Administration's Office of Advocacy and various higher ed and K-12 associations wrote to OMB and DOJ stating that small public entities in particular lack the staffing, budget, and in-house technical expertise to hit the original deadlines. DOJ now agrees.
- Technology that did not deliver as expected. DOJ says it overestimated how much generative AI and automated remediation tooling would reduce the manual workload. In their words, "advanced technology, such as generative AI, does not yet reliably automate the remediation of inaccessible content at scale." This is a significant admission, and worth remembering the next time a vendor pitches an AI-powered one-click accessibility solution.
- Notice concerns with the dynamic WCAG links. The 2024 rule incorporated the June 2018 static version of WCAG 2.1. But the WCAG reference pages include links to supplementary materials that change without notice. DOJ argues that creates liability exposure without fair notice to regulated parties. This is a preview of something they may revisit substantively in future rulemaking.
- Litigation risk they can't mitigate. DOJ notes that because Title II includes a private right of action, the Department cannot simply issue a non-enforcement policy. Only a rule change can provide real relief. Hence the IFR.
DOJ also signaled future rulemaking. In the IFR's own words: "the Department plans to engage in future rulemaking processes related to the substantive requirements of the 2024 final rule. During the extension period, the Department will consider issuing an NPRM providing members of the public with an opportunity to comment on the substance of the 2024 final rule and any changes proposed by the Department."
Translation: this is not the end of the rulemaking. It's the intermission. The substance of the rule could still change.
What the ADA Deadline Extension Means for Government Agencies
Let's be direct.
If you're a large public entity that was scrambling to meet the April 24, 2026 deadline: breathe, then don't stop. You now have 12 months of real working time. Use it to build something defensible instead of something desperate.
If you're a small public entity or special district that had been counting on April 26, 2027: you have two years now. That sounds like a lot. It is not. Two years is a single procurement cycle. A single CMS migration. A single round of PDF remediation across a reasonably sized document library.
If you're a vendor, contractor, or service provider to covered entities: your contractual obligations did not change. Most Title II procurement language references WCAG 2.1 AA conformance as an ongoing requirement, not one tied to the federal deadline. Expect covered entities to push accessibility language deeper into new contracts, not less.
If you were hoping the rule would be rescinded entirely: DOJ explicitly rejected that framing. They extended the deadline. They preserved the rule. They are planning more rulemaking.
Five Moves to Make in the Next 30 Days
Extensions are only useful if you use them.
1. Update every piece of content, every contract, and every internal document that references April 24, 2026 or April 26, 2027 as a deadline. Your RFP templates, procurement language, internal compliance timelines, board presentations, and public-facing accessibility statements all need to reflect the new dates. Inconsistency here is a litigation tell.
2. Do the inventory you skipped last year. Most public entities we work with cannot produce a current, accurate inventory of their websites, subdomains, mobile apps, hosted documents, third-party embeds, and vendor-delivered content. You cannot remediate what you cannot count. This is the foundation.
3. Get your baseline audit done now, not in Q4. Automated scans catch roughly 30 to 40 percent of WCAG issues. Manual testing by someone who actually uses assistive technology catches the rest. If you haven't done a comprehensive baseline that combines both, you are operating in the dark. Every month you wait, the remediation backlog grows, and your defensibility story gets thinner.
4. Build the five documents DOJ asks for in enforcement. An accessibility policy. A designated coordinator. A remediation plan with prioritization logic and timelines. A vendor and procurement standard. An ongoing monitoring and training program. These are the documents that distinguish "we had a plan and we were executing it" from "we had nothing and we got caught." This is the defensibility story.
5. Stop shopping for overlay widgets. The FTC's fine against accessiBe exists. AudioEye, UserWay, EqualWeb, and the rest of the overlay category continue to settle their own litigation. Overlays do not produce WCAG 2.1 AA conformance. They produce a false sense of security and a sticker on your homepage that plaintiffs' attorneys have learned to screenshot.
The Part Most Will Get Wrong
The single most predictable response to this IFR is the wrong one: treat it as a pause.
Here's why that fails.
The 2024 rule did not invent Title II accessibility obligations. It clarified them. DOJ has been enforcing web accessibility under Title II through settlement agreements for more than a decade. The 2026 and 2027 deadlines were specific to the new technical standard. The underlying obligation was already there, and it is still there.
State-level enforcement is also accelerating independently of the federal timeline. Colorado's HB 21-1110 is already in active enforcement with real monetary penalties. New Mexico's HB 295 requires WCAG 2.1 AA conformance for all state agencies by April 1, 2027. California has active legislation. Minnesota, Illinois, New York all have their own regimes forming.
The federal deadline moved. The state landscape kept moving forward. The lawsuit landscape kept moving forward. The only variable that actually shifted is the amount of runway you have to do this correctly.
What Comes Next
A few things to watch over the next 12 months.
The comment period. It opens Monday, April 20, 2026 and runs 60 days. Submit via regulations.gov with "RIN 1190-AA82" in the subject line, or reference Docket No. CRT150. If you have specific implementation data, share it. DOJ is explicitly soliciting feedback on whether the extension should be longer, shorter, or accompanied by other substantive changes.
The NPRM DOJ signaled. A Notice of Proposed Rulemaking revisiting the substance of the rule is on the table. Potential targets based on the IFR's reasoning: the incorporation-by-reference mechanism for WCAG, the treatment of dynamic standards, exemptions or modified obligations for very small entities, and possibly the treatment of AI-generated content.
Potential legal challenges. The disability rights community was strongly opposed to any extension. The National Federation of the Blind and allied organizations had been pushing for the original deadlines to hold. A challenge to the IFR on APA or other grounds is possible, though the "good cause" justification DOJ used is well-established.
State-level acceleration. Expect several states to use this as an opportunity to codify their own standards on shorter timelines.
The Main Thing
One year. That's the change.
Everything else, the rule, the standard, the substantive obligations, the litigation risk, the state-level enforcement landscape, the underlying civil rights framework, is exactly where it was on Thursday.
The organizations that use this extension to build a defensible compliance program will come out of 2027 stronger, less exposed, and more trusted by the residents they serve.
The organizations that treat this as a reason to stop will spend 2027 and 2028 doing the same work under more pressure, with less time, and without the benefit of learning from the mistakes everyone else is making right now.
Pick the first group.
Need a clearer picture of where you actually stand?
Our free ADA Risk Assessment gives you a prioritized view of your site's current accessibility state, mapped against WCAG 2.1 AA and against the five documents DOJ requests in enforcement proceedings. No overlay pitch. No 40-minute sales call required.
Start your free ADA Risk Assessment →
Sources
- DOJ Interim Final Rule (public inspection PDF): https://public-inspection.federalregister.gov/2026-07663.pdf
- Federal Register listing (goes live April 20, 2026): https://www.federalregister.gov/d/2026-07663
- Docket and comment portal: regulations.gov, Docket No. CRT150, RIN 1190-AA82
- 2024 final rule (unchanged): 89 FR 31320 (April 24, 2024)
Related Articles:
How to Write Alt Text for Government Images, Charts, and Maps
How to Audit Your CMS for Accessibility
How to Train Your Government Staff on Accessibility
FAQ: ADA Deadline Extension
Was the ADA deadline extended?
Yes. One year for both compliance tiers.
Does this reduce lawsuit risk?
No. Title II obligations and private lawsuits remain unchanged.
Do we still need to follow WCAG 2.1 AA?
Yes. The standard remains unchanged.
Should we slow down our accessibility efforts?
No. The extension is time to build a defensible program, not delay.