ADA Title II Compliance Deadline Extension: What Changed and Why It Matters

Introduction

In April 2024, the U.S. Department of Justice (DOJ) issued a final rule under Title II of the Americans with Disabilities Act (ADA) requiring state and local governments to make their websites, mobile applications and digital documents conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. The rule gave governments with populations of 50,000 or more until April 24, 2026, to comply, and smaller jurisdictions until April 26, 2027.

Back in 2024, we touched on everything you need to know in a post on Navigating the new Digital Accessibility Requirements.

If you read our industry update newsletter or are in any way involved in accessibility, this is likely something you’ve heard a lot about already, so we won’t reiterate the finer details here.

On April 20, 2026, the Monday morning before the first deadline was set to drop, the DOJ issued an Interim Final Rule (IFR) extending the compliance dates citing a need to re-evaluate implementation challenges. We read through comments from accessibility consultants, numerous organizations, the wider community, and of course the update’s 55 pages so you don’t have to.

This post aims to shed some light on what changed, why the deadlines were extended, whether we think the reasons are valid, and what may happen next.

The Changes

The Interim Final Rule moved each deadline one year later:

• Anyone serving a population of 50,000 or more: April 26, 2027
• Anyone serving a population under 50,000 (or special districts): April 26, 2028

The extension does not alter the scope or technical requirements in any way.

There was some confusion around the original deadlines because the compliance date for institutions serving 50,000 or more people was April 24, while the date for those serving fewer was April 26. Both now land on April 26 of their respective years.

The IFR took effect upon publication but invites public comments until June 22, 2026 (more on that below).

Why Extend the Deadlines?

The DOJ cited several reasons for extending the deadlines based on feedback they received following a request for comments on deregulation in April 2025. These reasons fall into a few broad categories.

Resource Constraints and Staffing Limitations

A May 2025 letter from the American Council on Education, signed by 15 higher education associations, asked OMB to pause implementation. The letter said member institutions were preparing for the deadlines, but that doing so was eating into staff time and budget, and that institutions were still working through compliance challenges.

The Small Business Administration’s Office of Advocacy went further by saying that the DOJ had underestimated the costs and burden of the 2024 rule, that small public entities lack the staff and technical expertise to comply, and that the original timeline was too tight. They originally recommended a runway of 4 to 5 years for entities serving fewer than 50,000 people, and added the rule to its “small-businesses-most-wanted-reform” list.

A coalition of elementary and secondary education associations surveyed 60 of their members. Many said they would need new hires to comply, that they would struggle to absorb the costs, and that they worried about a litigation rush. Some also argued that a hard deadline pushes institutions into procedural box-checking rather than building sustainable programs.

We have heard each of these points from people on the ground, and they are valid. Unfortunately, equally valid is that without the threat of litigation, accessibility is rarely prioritized at all.

Misinterpretation of Dynamic References

The 2024 rule incorporated WCAG 2.1 by reference and linked to supplementary WCAG materials that could be updated by the World Wide Web Consortium. The IFR warns that if the linked documents change, governments might not have fair notice of new obligations. As such, covered entities fear that changes to WCAG outside of the DOJ’s control could trigger lawsuits. On its face this could sound convincing. If requirements change without warning, institutions could suddenly fall out of compliance through no fault of their own. Except this is not how WCAG works in practice:

• This is not how the W3C’s editorial process works (see section 6.3.1 under “W3C Recommendation”). “After its initial publication, a W3C Recommendation may be revised (in accordance with §§6.3.10 Revising a W3C Recommendation) to address editorial or substantive issues that are discovered later.” New features can only be added if the document explicitly says that this is allowed, which WCAG 2.1 does not. Features require creating another edition, like WCAG 2.2.
• Since WCAG 2.1 was made an official recommendation, all edits (which can be found in the changelog at the bottom of the page) are cosmetic: things like format modifications, clarification on definitions, and typo corrections. Retroactively changing the guidelines would directly go against the credibility of the W3C, which is already relied upon for standards internationally.
• All of the links in the WCAG 2.1 document jump the user to WCAG 2.1 information when clicked, including the “how to meet document”, which explicitly includes a “?versions=2.1” URL parameter. Put simply, it is not likely that someone will assume version 2.2 requirements apply to version 2.1. We have never been asked this question in the course of completing hundreds of audits since WCAG 2.2 was released in October 2023.
• The official WCAG 2.1 reference is the only document officially designated as a “recommendation”. All other materials are supplementary, supporting documents.
• The DOJ has historically recommended complying with WCAG in court orders, consent decrees, and settlements.
• The IFR points to a banner at the top of the WCAG 2.1 page reading “This version is outdated!” as a source of confusion. That banner only signals that a newer version (2.2) exists. It does not retract 2.1, and the same convention applies to every superseded W3C Recommendation. Reading “outdated” as “invalid” would be a misunderstanding of how W3C documents work, not evidence that the standard is unstable.

Further, by calling WCAG “unknowable”, the DOJ has handed defendants a new argument predicated on misinformation. We expect to see this argument used sooner rather than later.

Technical Limitations (GenAI and STEM Content)

The IFR notes that agencies increasingly use generative AI tools to produce content, but AI does not reliably create accessible outputs and cannot “automate remediation” at scale. DOJ cites a National Association of Counties survey indicating that roughly 60% of counties use generative AI in monthly operations, raising the concern that AI image generation does not always produce accurate alternative text, and outputs based on inaccessible inputs tend to remain inaccessible.

This is almost entirely false. Accurate alternative text descriptions can be generated with the right prompts and workflows. The need for prompt solutions in response to the final rule has spawned a new category of GenAI-based products that remediate PDFs at scale and with a high degree of accuracy, like DocAccess and Scribe. From this perspective, legislation is encouraging innovation.

However, this is beside the point. The 2024 rule does not require agencies to use generative AI. In fact, AI is mentioned nowhere in that publication. It simply requires the resulting content to be accessible. If AI is used to help an organization get there more quickly, that’s excellent! If the chosen tool produces inaccessible output, the fix is the workflow (alter the input, use a different tool, or add a human in the loop), not the deadline.

AI is not the only answer, though, and overuse adds risk of producing inaccessible content faster than people can clean it up.

The STEM concern is a bit more substantive, but it is not new. MathML, alternative text conventions for scientific content, and resources on building effective data visualizations have been around for years. The hard part is not how to make STEM content accessible, but whether organizations have invested in the workflows to do it. That investment is exactly what the rule was supposed to drive.

Our Thoughts

This development is good for us as an organization, but disappointing and problematic for us as taxpayers.

The Good

Many accessibility service providers will say this is unequivocally bad, or that it is yet another step back for civil rights. We tend to disagree.

Most of the people that we have been talking to are making good progress, but they are not even close to ready.

When you give every state and local government 2 to 3 years (depending on size) to fix potentially thousands if not hundreds of thousands of PDF documents, hold vendors accountable, consider replacing vendors that don’t meet their obligations, roll out training, audit and fix issues across their many websites… It is going to be done in a way that might not be the most maintainable, despite the best intentions to the contrary. Good accessibility is repeatable, something that people do not because they are forced into it, but because it is habitual and they understand and believe in the mission. Cultivating that mindset is not something you can feasibly do in two short and potentially stressful years.

The approach that many organizations (especially those with limited resources) feel forced to take is unfortunately not one that will bring about the meaningful change that advocates and people with disabilities want to see. There needs to be a balance between swift implementation and a sustainable pace that does not lead to burnout. For some organizations, the extra wiggle room might be just what they need to find this balance.

The Bad

While organizations get more time, the cost ultimately falls on the people the rule is meant to protect. Title II litigation over the last several years has produced a documented record of people locked out of public services that their tax dollars fund: voters who struggle to independently read ballot materials, residents unable to apply for services, difficulty paying bills (with no allowances for delays), and of course students cut off from course content. These are not hypothetical issues, and organizations can still be sued for noncompliance today. The extensions create an impression that the work matters less, that the regulation may continue to fall under attack, and that litigation will be put on hold. People with disabilities have waited over twenty years for the digital side of public services to catch up. Another year is another year of lost access.

The framing of the WCAG as “unknowable” is perhaps the most worrying piece buried within the IFR. Despite being demonstrably false, defendants in private accessibility suits will lift it directly since it has now been elevated to the level of an official federal position.

The IFR signals that DOJ may issue a new NPRM during the extension period to revisit the substantive requirements of the 2024 rule. Read in context with the rest of the IFR, this starts to look less like a courtesy gesture and more like a runway for weakening the standard over time until there is little or nothing left. DOJ does say that if no NPRM is issued and no further delays are warranted, it “fully anticipates implementing the regulation at the new deadline”. But a year is more than enough time to issue a new NPRM and substantially weaken the rule.

Organizations that took the rule seriously and invested ahead of the deadlines are now competing internally for budget against organizations that did not. The Association on Higher Education and Disability and the National Federation of the Blind both raised a point in their comments: compliance does not stay funded when the people doing it look like they wasted their year.

DOJ’s own analysis estimates the one-year delay saves roughly $2.775 billion in present-value compliance costs over ten years. In the same analysis, the Department admits it could not quantify the impact on benefits, which is to say the offsetting harm to people who would have gained access to public services. A cost-benefit analysis with one side blank is the opposite of a fair or balanced metric.

Comment By June 22

The IFR took effect immediately on publication, but DOJ is accepting public comment through June 22, 2026. Given the signal that a follow-up NPRM may be issued during the extension period to revisit the requirements of the rule, feedback is more important now than ever before. Whatever shape the next round takes, comments are a matter of public record and will have a direct bearing on the future of digital accessibility for government services.

Comments from people doing the work tend to land harder than those made by people watching it from the outside, so if you have direct experience with this work (as a covered entity, a vendor, an advocate, or a person with a disability who relies on these services), please consider speaking up!

To file: go to regulations.gov and search for RIN 1190-AA82, or mail a hard copy to Disability Rights Section, Civil Rights Division, U.S. Department of Justice, 150 M St. NE, 10th Floor, Washington, DC 20002. Comments must be received by midnight Eastern on June 22, 2026.

The Path Forward

Looking ahead, we are hopeful that the extension will offer governments and vendors that have already begun to stand up accessibility efforts the chance to make these practices a normal part of everyday business. If approached correctly, the temporary breather could be just what these entities need to build out programs that scale over the long term. The work is important, but frantically jumping into it based on the fear of a pending deadline and potential litigation is a recipe for performative progress.

Disability advocates will likely challenge the IFR, probably with limited success. This will create some noise. If you are impacted, focus less on the headlines and the need to meet requirements by an arbitrary deadline. Think about how you can continue the work that you have already started. Use this additional time to conduct thorough audits, remediate high-impact content, train staff, embed accessibility into procurement, and monitor progress. Doing so will reduce legal risk and, more importantly, ensure that everyone can access government information and services on equal terms. We don’t say this out of a desire for business, but as a team of pragmatic people who live at an intersection of the needs of everyday residents with cognitive and physical impairments, and the organizations that serve them.

Deadlines are ephemeral. Doing the right thing is eternal.

Need Help Navigating This?

The extension gives covered entities a bit more runway, but the work itself hasn’t changed. If your team is figuring out where to start, where you stand, or how to build a sustainable accessibility program before the new deadlines, we can help. QualityLogic offers accessibility audits, remediation, and ongoing testing for state and local governments and the vendors who serve them. Get in touch to talk through your situation, or subscribe to our accessibility newsletter for monthly updates on regulatory changes, technical guidance, and practical insights from our team.

---