Every week, I have conversations with state and local government teams who have been heads-down preparing for the April 24, 2026 ADA Title II web accessibility deadline. On April 20, the DOJ officially extended it by a full year.
For large entities serving populations of 50,000 or more, the new deadline is April 26, 2027. Smaller entities and special district governments now have until April 26, 2028.
In this article, I’ll walk through what the extension actually changes, why the DOJ made this call, and most importantly, why the organizations that treat this as a green light to pause are taking on more risk, not less.
What the Rule Actually Requires
The DOJ’s final ADA Title II accessibility rule became effective June 24, 2024. For state and local government entities serving populations of 50,000 or more, the compliance deadline was originally April 24, 2026, which is now extended to April 26, 2027. Smaller entities and special district governments now have until April 26, 2028.
After your applicable deadline, any web content or mobile app your organization provides, including anything delivered through vendors, third-party platforms, or contracted services, needs to meet WCAG 2.1 Level AA compliance.
Ensuring digital experiences that your team develops or coded can be simple to understand. But for many organizations that we work with, most of their digital experiences are owned or contracted through a third-party company or vendor. That “through contractual arrangements” language in the DOJ ruling is one of the most important parts of the rule to understand. Meaning, even if a vendor built your webpage or you purchased an app to allow constituents to pay for public parking, your organization is still responsible for its accessibility. You can’t outsource the obligation.
If a county web page lists the addresses and hours of operations for all county parks, that web page must meet WCAG 2.1, Level AA even if a local web design company made the web page and updates it for the county.
ADA Title II Web Accessibility Rule Fact Sheet (2024)
Now, the rule does come with some built-in flexibility that a lot of organizations either overlook or misuse:
- Defined exceptions exist for archived content, certain older documents, content posted by unaffiliated third parties, some password-protected documents, and preexisting social media posts.
- Conforming alternate versions are permitted, but only in narrow situations where direct accessibility genuinely isn’t possible due to technical or legal limitations.
- Undue burden and fundamental alteration limitations still apply, though they don’t eliminate the obligation entirely. You’re still required to provide access “to the maximum extent possible.”
- A minor nonconformance provision (28 C.F.R. § 35.205) exists for issues with minimal impact on access, but the burden is on your organization to demonstrate that with evidence.
These are narrow exceptions, and the DOJ is explicit about that.
What the DOJ’s Extension Actually Says
On April 20, 2026, the DOJ published an Interim Final Rule (IFR) officially extending the compliance deadlines. The IFR is already in effect, and a public comment period runs through June 22, 2026.
The DOJ was direct about why: it overestimated how ready covered entities would be. Staffing and budget constraints, the complexity of remediating large and technically dense content sets, and the current limitations of AI-assisted remediation were all cited as factors. In plain terms, they looked at how things were going on the ground and gave organizations more runway.
Naturally, those reasons are a hot debate in the accessibility community. Many argue the extension is unwarranted, and that organizations impacted by the ruling have had plenty of time to prepare. Others explain that the DOJ’s reasoning on “limitations of AI-assisted remediation” do not make sense, as AI was never considered or popularly used when the initial ruling was passed. The fact is, the extension the DOJ provided follows similar steps that Colorado used when they passed a similar accessibility law (HB21-1110), where they extended it another year towards at the “finish line”. If the Title 2 ruling continues this trend of following HB21-1110, I do not anticipate another extension will be presented or passed. Opinions aside, this brings us to an important point…
Here’s what the IFR explicitly does not do: it does not suspend Title II’s underlying nondiscrimination and effective communication obligations. Those have been in place for decades and remain fully intact. The technical deadline moved. The civil rights obligation didn’t.
Why the Extension Doesn’t Change Your Underlying Obligations
ADA Title II already required state and local governments to ensure equal access to their services, including digital experiences, long before the 2024 final rule existed. The DOJ has consistently held that position for decades. The technical standard is new. The civil rights obligation is not.
Two legal anchors make “the deadline moved, so we can wait” a risky argument:
First, Title II’s general nondiscrimination rule prohibits excluding people with disabilities from your services, programs, or activities. And its effective communication requirement means your digital communications need to be just as effective for people with disabilities as they are for everyone else.
Second, Title II has real enforcement teeth, including reasonable attorney’s fees, litigation expenses, and costs that can be awarded to prevailing parties.
For organizations that receive federal financial assistance, Section 504 adds another layer of exposure that the DOJ has addressed in guidance for years.
And here’s one more thing worth knowing: the 2024 rule covers web content and mobile apps specifically, but the DOJ made clear that existing Title II obligations continue to apply to other digital technologies too. Digital accessibility is a continuing civil rights obligation, and the deadline is just one milestone in a much longer journey.
So What Do You Do With the Extra Time?
You have a cleaner runway than you did weeks ago. The question is whether your organization will use it, or let the new deadline become the same kind of last-minute scramble.
The most effective posture right now focuses on three things: stopping new accessibility problems from being introduced, reducing risk in your highest-impact services, and building a documented compliance record that demonstrates your organization is treating this as an ongoing operational requirement, not a one-time checkbox. Here’s how that looks in practice.
Stop making things worse, immediately.
The exceptions that exist for “preexisting” content don’t protect anything newly posted or updated after your compliance date. So the fastest thing you can do right now is make sure every new or updated page, PDF, form, or video your teams publish doesn’t introduce known WCAG 2.1 AA barriers.
Practically speaking, that means building checkpoints into the workflows of your highest-volume publishing teams: communications, HR, public meetings, benefits, and procurement. Templates, publishing rules, trained reviewers. Whatever it takes to put a gate between your team and new noncompliance.
Triage based on real user impact.
Ask yourself: where are people most likely trying to use our services online? Start there. That usually means high-traffic, high-consequence pages like benefits eligibility, payments, permits, elections information, and public safety. And don’t forget anything delivered through vendors or third-party platforms, because your organization is still on the hook for those too.
Use exceptions wisely.
Exceptions exist for legitimate circumstances, they require documentation, and they’re not meant to be a blanket workaround. The DOJ is explicit: exceptions don’t eliminate your broader duty to provide effective communication and equal access.
A few smarter ways to handle exceptions:
- Build a genuine archive pathway that actually meets DOJ criteria: created before the compliance date, kept for reference only, not updated since.
- For older PDFs that qualify for the preexisting documents exception, create a quick-response process to deliver accessible versions on request. Effective communication obligations still apply.
- For platforms where the public posts content, carefully document what’s truly third-party versus what’s posted by vendors or contractors, because the exception doesn’t cover the latter.
Create an accessibility request and issue-reporting channel that actually works.
Give the public a way to report problems and request accessible formats, and then actually respond. Beyond being good practice, it’s a meaningful risk-control mechanism. Responsiveness can prevent an issue from escalating into a formal complaint or investigation, and it’s one of the clearest ways to demonstrate active compliance management.
Don’t build your strategy around “separate accessible versions.”
It’s tempting. But the DOJ is clear that maintaining an inaccessible main experience alongside a separate accessible one is generally not allowed. Conforming alternate versions are only permitted under very narrow technical or legal limitations. If you’re relying on this approach, make sure you can support those conditions under the rule. Otherwise, it’s a risk.
Building a Compliance Record That Holds Up
A strong compliance posture isn’t about claiming perfection. It’s about being able to show with real evidence that your organization has built processes that produce accessibility, and that you can justify edge cases using the rule’s own built-in limitations.
Several parts of the rule explicitly place the burden on the public entity to justify deviations. That means documentation isn’t optional. It’s your defense.
Here’s what a defensible compliance record tends to include:
- Written policies for what must be accessible and how publishing works. Nobody will ever be 100% compliant, so policies provide evidence of institutional intent. Think of them as your paper trail that shows accessibility is being governed.
- An inventory and prioritization plan tied to real services and usage. If you’re ever challenged, a remediation roadmap visibly focused on core services is far easier to defend than one that looks arbitrary. Prioritize what matters most to the people you serve.
- A vendor accountability file. Because the rule covers everything your organization provides, which includes services through vendors, vendor management is a compliance function now. Review your contracts and document your vendors’ obligations. The DOJ’s guidance is direct: governments must ensure contracted services comply, including vendor-hosted apps and vendor-posted content. This will be especially important as you negotiate renewals.
- A structured approach to exceptions. Treat exceptions as tracked categories, not just informal judgments. For each exception you’re relying on, document what qualifies, why it qualifies, and how users can still request access. The DOJ is clear that exceptions don’t eliminate effective communication duties, and being able to demonstrate that quickly goes a long way toward credibility.
How to Talk About the Extension Without Letting It Become an Excuse
It’ll be common to hear team members say, “Great, we have another year, let’s revisit this later.” You should be prepared to push back on that directly.
Acknowledge the extension. It’s real, and it gives your organization more time to do this right. But pivot quickly: the underlying civil rights obligation has been there for decades, the IFR itself confirms that nondiscrimination duties remain fully in effect, and the organizations that use this time well will be in a fundamentally better position than those that hit pause again.
The simplest, most defensible way to frame it internally: the rule is in effect unless and until it changes, and accessibility obligations remain either way.
How Nelnet Digital Services Can Help
Your challenge over the next year won’t only be about catching up. It’s about building a program you can sustain. Nelnet Digital Accessibility Services supports exactly those needs:
- Accessibility assessments to identify barriers, manage compliance risk, and give your team detailed, actionable guidance on where to focus.
- Remediation services for websites, mobile apps, documents, and videos, making sure they work with assistive technologies like screen readers.
- Training to help your teams build accessibility into everyday workflows, so compliance becomes a repeatable practice instead of a recurring scramble.
- Governance support to help you establish a sustainable accessibility program: policies and standards, roles and responsibilities, review cadences, reporting, and vendor oversight.
The DOJ rule gives public entities a clear, testable technical baseline in WCAG 2.1 AA. The extra year isn’t a reprieve, but instead an opportunity to build the kind of program that holds up over time and genuinely serves the people who depend on your services.
Ready to take the next step? Reach out to our team for an assessment, and let’s build a roadmap that works for where you are right now.
