On April 20, 2026, the Department of Justice published an Interim Final Rule pushing back the compliance dates for its 2024 Title II web accessibility rule. If you’re an IT or communications director for an Oklahoma city, county, or state agency, you’ve probably already read the headline: you have more time. What matters more is what you do with it.
What actually changed
The DOJ extended both compliance dates by one year:
- State and local government entities serving populations of 50,000 or more: moved from April 24, 2026 to April 26, 2027.
- Smaller entities and special district governments: moved from April 26, 2027 to April 26, 2028.
That’s it. The technical standard itself — WCAG 2.1 Level AA — did not change. The scope of what’s covered didn’t change. And critically, the underlying ADA obligation to provide accessible services didn’t change either. The DOJ was explicit that this rule “does not alter any other provisions of the 2024 final rule.” It moved a date. Nothing else.
Why the DOJ moved the date
In its own commentary, the DOJ cited three reasons: it overestimated how ready public entities’ technology and staffing actually were, automated remediation tools still can’t reliably handle complex content without human review, and entities faced significant litigation exposure trying to hit the original deadline unprepared. In short, the deadline was unrealistic, not the requirement.
The DOJ also noted it may pursue further rulemaking to revisit the substantive requirements down the road, and floated a possible separate rulemaking narrowly focused on K-12 schools. Neither has happened. The public comment period on this interim rule closed June 22, 2026, and no new proposed rule has been published as of this writing. Read: nothing is confirmed to change further. Plan around the rule as it stands today, not around rumors of what it might become.
Why you shouldn’t read this as a pause button
Two things are still true regardless of the new deadline:
First, the DOJ intends to enforce these dates when they arrive — it said as much directly, warning it “fully anticipates implementing the regulation at the new deadline.” A 2027 or 2028 date that arrives with your site untouched puts you in the same bind current entities were in this spring, just a year later.
Second, and more immediately relevant: private ADA lawsuits are not paused by this rule at all. The compliance date extension is specific to DOJ’s Title II regulation. General ADA accessibility obligations, and the litigation risk that comes with an inaccessible public-facing site, exist independently of that regulatory clock. An extension on paper doesn’t change what a resident using a screen reader can or can’t do on your site today.
Entities that treat this as “we’re off the hook” are the ones who’ll be scrambling — and litigated against — in 2027. Entities that treat it as what it actually is, a head start to do the work properly instead of rushed, will be the ones sitting comfortably when the new date lands.
What to do with the extra time
If you’re serious about using this time well, the sequence is the same one we’d have recommended in any accessibility engagement, just without the panic:
- Audit. Get a real WCAG 2.1 AA audit — automated scans catch maybe 30–40% of issues, so it needs manual testing and assistive technology review from someone who does this regularly, not just a plugin report.
- Remediate. Prioritize by traffic and risk: your homepage, forms, PDFs, and any transactional pages (permits, payments, applications) go first. Save low-traffic archive pages for later, since the rule already carves out narrow exceptions for genuinely archived content.
- Document. Keep a written record of what you audited, what you fixed, and when. If a complaint or lawsuit does land, a documented, in-progress remediation effort reads very differently to a court than radio silence.
- Train. Whoever is publishing content on your site day-to-day — comms staff, department admins — needs to know the basics: alt text, heading structure, link text, color contrast. Otherwise you’ll re-break what you just fixed with the next blog post or PDF upload.
That’s the whole playbook. It’s not complicated. It just takes someone actually doing it instead of waiting for the next deadline to force the issue.
Where we fit in
We specialize in WCAG 2.1 AA compliance and remediation for Oklahoma government and higher education clients, and we’re a prequalified vendor under SW0135 for state procurement — so bringing us in doesn’t mean starting a new RFP from scratch. If you want the full breakdown of how we approach this work, see our ADA-compliant web design and WCAG 2.1 AA accessibility services page.
The extension bought you time. It didn’t buy you an exemption. If your last accessibility audit predates this rule — or you’ve never had one — now’s the moment to use the extra time instead of letting it slip by.