On April 17, 2026, the Department of Justice issued an Interim Final Rule extending the compliance dates in the 2024 Title II web rule by one year.
Large public entities (populations of 50,000 or more) now have until April 26, 2027. Entities under 50,000 and special district governments have until April 26, 2028.
The IFR is effective immediately. WCAG 2.1 Level AA remains the technical standard, and no substantive requirement has changed. DOJ is accepting public comment through June 22, 2026, and has signaled it may issue a new proposed rulemaking on the rule's substance during the extension period. This post has been updated to reflect the extension.
This article is based on real-world guidance from UsableNet’s work with public sector organizations preparing for ADA Title II digital accessibility requirements now in effect.
The deadline moved — but the obligation didn't.
On April 17, DOJ extended the Title II web accessibility compliance dates by one year. Large public entities now have until April 26, 2027. Smaller entities and special districts have until April 26, 2028. The extension is a direct response to feedback from state and local governments, higher education associations, and the Small Business Administration's Office of Advocacy, all of whom told OMB the original timelines weren't achievable given staffing and technology realities.
The extension is not a reprieve from the underlying requirement. WCAG 2.1 Level AA still applies. Third-party vendors are still in scope. Title II's underlying nondiscrimination obligation has been in effect for decades. What agencies have now is 12 more months — and a choice about how to use them.
The agencies in the strongest position a year from now will not be the ones who treat this as a pause. They will be the ones who use the extension to build a defensible, documented program instead of rushing through procedural box-checking.
Key Takeaways
- The compliance deadline is now April 26, 2027 for large public entities and April 26, 2028 for smaller entities and special districts
- WCAG 2.1 Level AA remains the required technical standard
- Accessibility obligations still extend to vendors, apps, and third-party tools
- The extension is an opportunity to build a sustainable program, not to delay starting
- DOJ has signaled it may revisit the rule's substance during the extension period — organizations should monitor but not wait
- Automated testing alone identifies only a portion of real accessibility issues
- A documented plan is the core of a defensible posture, regardless of deadline
Common Misconceptions About ADA Title II
Many organizations are still operating under outdated assumptions about what ADA Title II requires.
Myth: "The extension means we can pause accessibility work."
Reality: Title II at its core says public entities must already be accessible. That obligation predates the 2024 rule by decades. The extension moved the timeline for the new technical standard — not the underlying duty. Private litigants retain a right of action, and complaints and accommodation requests still generate legal exposure regardless of the April 2027 or 2028 dates.
Myth: “We just need to make our website accessible.”
Reality: ADA Title II applies to websites, mobile apps, social media, and third-party tools—not just your homepage.
Myth: “Our vendor handles accessibility.”
Reality: If a vendor supports your services, your organization remains responsible for ensuring that content and functionality are accessible.
Myth: “We can wait for a complaint before acting.”
Reality: ADA Title II requires proactive accessibility. Waiting for a request or complaint is not a compliant approach.
Myth: “Existing content is automatically exempt.”
Reality: Limited exceptions exist, but many types of content still require review, evaluation, and documentation to determine whether they meet accessibility requirement
Digital accessibility is now an explicit legal requirement
ADA Title II has always required equal access to programs and services.
What has changed is this:
Digital accessibility is now explicitly defined and enforceable.
Public entities must ensure accessibility across:
- Websites
- Mobile applications
- Online services such as payments and applications
- Digital content delivered through third parties
If a user cannot complete a transaction independently, the experience is not compliant.
Vendor tools are a major source of hidden risk
Many accessibility gaps originate from third-party tools.
Payment systems, scheduling platforms, and other vendor-provided services are often unaudited and assumed to be compliant.
Every unaudited vendor tool is an open, unquantified exposure.
If vendor tools are not audited, the organization still carries the liability.
If it is part of your service delivery, it is part of your compliance obligation.
Not everything must be fixed immediately—but everything must be evaluated
The scope of accessibility can feel overwhelming, especially for large organizations.
The regulations include limited exceptions, such as:
- Archived content
- Pre-existing documents created before the deadline
- Certain individualized, secured documents
However, these are not shortcuts.
If you rely on an exception, you must formally document and justify that decision.
Compliance is not about perfection overnight. It is about making informed, defensible decisions.
Prioritization is the most important step right now
Trying to fix everything at once is not realistic.
Organizations need to focus on:
- Core public services (payments, applications, benefits access)
- High-impact user journeys
- Frequently used digital content
If users cannot complete essential tasks, you already have a meaningful accessibility risk.
A scan report is not a defense
Automated tools are useful, but incomplete.
They typically identify only a portion of accessibility issues. Many WCAG requirements require manual validation using assistive technologies.
A scan catches only a fraction of accessibility barriers. The majority of issues require manual testing and real user validation.
An accessibility audit that relies only on automated testing is not sufficient for compliance.
The extension is Not Permission to wait
When a deadline moves, the instinct in resource-constrained organizations is to reallocate attention elsewhere. That is the wrong read here.
The agencies using this extension well are doing three things: completing the audit and prioritization work that was rushed in late 2025, establishing ownership and governance across departments, and starting vendor remediation conversations that take months to resolve.
What enforcement risk actually looks like
The extension pushes out the deadline for the 2024 rule's specific technical requirements, but it does not pause ADA Title II enforcement more broadly. Private litigants can still bring claims based on the underlying nondiscrimination obligation. Agencies that ignore accessibility for another year face the same settlement pressure, injunctive relief, and attorneys' fees exposure they did before the extension.
Non-compliance can lead to:
- Department of Justice investigations
- Legal action by private parties
- Court orders requiring remediation
- Responsibility for attorney’s fees
These outcomes are not theoretical. Legal activity around digital accessibility continues to evolve, with enforcement coming from both regulators and private parties.
Enforcement does not require full non-compliance—failure to demonstrate a defensible accessibility program can be enough to trigger risk.
What a defensible accessibility program looks like
At this stage, public entities should be able to demonstrate:
- A documented accessibility roadmap with clear priorities and timelines
- Defined ownership across departments
- Ongoing audits that include manual testing
- Training for teams managing digital content
- Vendor requirements for WCAG conformance and accessibility documentation
- Written justification for any exceptions or limitations
A documented, ongoing accessibility program is required to maintain compliance as digital services evolve, including prioritizing remediation and maintaining accessibility across releases.
Accessibility is now an operational requirement, not a one-time project.
Common Questions
Has the compliance deadline changed?
Yes. On April 17, 2026, DOJ issued an Interim Final Rule extending both compliance dates by one year. Public entities with populations of 50,000 or more now have until April 26, 2027. Entities under 50,000 and special district governments have until April 26, 2028. The technical standard (WCAG 2.1 Level AA) and all substantive requirements remain unchanged.
Is DOJ going to change the rule further?
Possibly. In the IFR, DOJ stated it may issue a new proposed rulemaking on the substance of the 2024 rule during the extension period. Public comments on the extension are open through June 22, 2026. Organizations should monitor developments but should not delay compliance planning based on the possibility of further changes.
What standard is required right now?
WCAG 2.1 Level AA is the required standard for ADA Title II digital accessibility compliance.
How should we approach accessibility testing?
Accessibility testing should combine automated tools with manual validation using assistive technologies. Automated testing helps identify common issues at scale, but manual testing is required to evaluate usability and real user workflows. This combined approach creates a more complete and defensible record of accessibility efforts.
What if we are not fully compliant today?
Most organizations are not fully compliant today. The priority should be to establish a documented plan, define clear priorities, and demonstrate ongoing progress in addressing accessibility gaps.
Are third-party tools included?
Yes. If third-party tools support your services, they must meet accessibility requirements. The responsibility for accessibility remains with your organization, even if a vendor provides the technology.
Do we need to make all content accessible?
Not necessarily. Certain archived or pre-existing content may qualify for limited exceptions, but these cases must be evaluated carefully and documented. Organizations are still expected to provide accessible access to services to the maximum extent possible.
The extension changes the Timeline, not the Standard
WCAG 2.1 Level AA is still the rule. Vendors are still in scope. A documented, ongoing program is still what separates agencies with a defensible posture from agencies waiting for a complaint.
What has changed is this: public entities now have a realistic window to build the program rather than assemble it under duress. That is the opportunity — and the test of whether leadership treats accessibility as operational infrastructure or as a deadline to survive.
Take the Next Step
If you’re evaluating your current accessibility risk or need to build a defensible plan, our team can help.
Contact UsableNet to assess your digital properties, prioritize remediation, and implement a sustainable accessibility program.
