WCAG Mandate Is Extended a Year: What This Means for You and Your Company
The DOJ just handed organizations an extra year on their WCAG compliance deadline, but that doesn’t mean the work stops. If anything, it’s a signal to accelerate.
On April 20, 2026, the Department of Justice issued an Interim Final Rule extending the ADA Title II web accessibility deadline by one year. State and local government entities serving populations of 50,000 or more now have until April 26, 2027, to achieve full WCAG 2.1 Level AA conformance. Smaller jurisdictions have until April 26, 2028. For organizations that have already been tracking Oomph’s earlier breakdown of the WCAG compliance landscape, this is the latest update, and the stakes are higher than the extension might suggest.
The Extension Doesn’t Change the Underlying Obligation
The DOJ’s rule revision pushes a deadline. It doesn’t remove one. WCAG 2.1 Level AA remains the legal standard under the ADA, and the obligation to make digital content accessible to people with disabilities has been codified since the original Title II rule was finalized in April 2024. The extension was issued in response to documented capacity constraints; some organizations were struggling with the scope of remediating thousands of PDFs and auditing vendor platforms. But organizations that have paused work in anticipation of a rollback shouldn’t interpret this as a signal to wait longer.
Private litigation hasn’t paused. ADA Title III lawsuits, which apply to private businesses, saw a 102% increase in recent years and aren’t tied to the DOJ’s enforcement calendar.
What the New Deadlines Mean for Your Organization
The updated compliance schedule breaks down by entity type:
- State and local governments (50,000+ population): April 26, 2027
- State and local governments (under 50,000 population) and special districts: April 26, 2028
- Private organizations that contract with or provide digital services to public entities: bound by the deadlines of their government partners, with contractual accessibility provisions becoming standard in procurement
If you work with public sector clients, including healthcare systems, universities, or municipalities, your contracts will increasingly reflect these requirements. Vendors are legally responsible for the accessibility of the tools and platforms they provide to covered entities. An extended deadline for your client doesn’t reduce your exposure.
Why an Extra Year Is Actually an Opportunity
Organizations that treat this extension as breathing room will spend it the same way they spent the last two years: waiting. The ones that use it intentionally will close the gap permanently.
True WCAG compliance requires more than fixing what’s broken today. It means building accessibility into your content production process, your procurement checklist, and your development workflow so that new content is compliant from the moment it’s published. There’s no grandfathering for content published after the compliance date; anything that goes live after your deadline has to meet the standard on day one.
The extension also offers something the original deadline didn’t: time to do the audit properly. A comprehensive audit, one that combines automated scanning with manual testing and includes real users with disabilities, takes time to execute and even more time to act on. Organizations that use this year to conduct a thorough audit, triage findings by risk, and implement remediation systematically will be in a fundamentally stronger position than those who rush a surface-level fix in the final weeks before a hard deadline.
What to Prioritize Now
The compliance work that matters most isn’t complicated, but it does require deliberate sequencing. Start with an honest inventory of what you have: web pages, PDFs, forms, video content, mobile applications. Identify which assets carry the highest user traffic and the highest legal exposure. That’s where remediation starts.
From there, the priorities are consistent regardless of organization type:
- Audit your highest-traffic pages and mission-critical digital services first.
- Address the underlying code. Overlay widgets don’t satisfy the standard and have been explicitly called out by the DOJ as insufficient.
- Review vendor contracts and confirm that third-party platforms in your digital ecosystem meet WCAG 2.1 Level AA.
- Build an accessibility policy that defines ownership, sets standards for new content, and creates a process for users to report issues.
- Train staff who create and publish digital content, not just developers.
The organizations that will find April 2027 manageable are already working through this list. The ones who don’t have 12 months to close a gap that was supposed to be closed already.
The Bigger Picture Hasn’t Changed
The DOJ’s extension is administrative. The underlying direction of travel toward universal, codified digital accessibility standards has been consistent for years and isn’t reversing. WCAG 3.0, expected no earlier than 2028, will shift from a pass/fail model to a tiered scoring system with Bronze, Silver, and Gold levels. Organizations that achieve full WCAG 2.1 Level AA conformance now will enter that transition from a position of strength.
