The DOJ just bought state and local government sites another year on web accessibility — which means institutions that read "extension" as "extension of time to not think about it" are already behind.
We’ve had this conversation twice already this year. A client — health system, university department, nonprofit with state contracts — mentions they saw something about a web accessibility deadline being pushed back and asks whether they still need to worry about it. The answer, both times, was yes. The extension is real. The deadline is not gone. And nine months is not as much runway as it sounds when you’re talking about a large WordPress site.
Here’s what actually happened. In April 2026, the Department of Justice issued an Interim Final Rule extending the ADA Title II compliance deadline for state and local government entities serving populations of 50,000 or more. The new deadline is April 26, 2027. Smaller entities and special districts get until April 26, 2028. The rule took immediate effect. The public comment window closed June 22, 2026. The underlying standard hasn’t changed: WCAG 2.1 Level AA, the same benchmark it’s been since the original rule.
The practical implication for our clients is direct. Health systems, university departments, and nonprofits that operate sites serving public-sector partners or receive federal funding sit inside Title II’s reach — or close enough to it that the distinction rarely matters when a complaint lands. The one-year extension was granted because entities needed more time to come into compliance. It was not granted because the requirement softened.
A full WCAG 2.1 AA audit plus remediation on a large site typically takes three to six months. April 2027 is nine months out. The math works — but only for institutions that start now.
The pattern we see is predictable. An institution reads “deadline extended” and files it under resolved. Budgets get set without an accessibility line item. Then February arrives, someone flags the deadline internally, and the call comes in frantic. We’ve done emergency remediations. They’re doable. They’re also more expensive, more compressed, and harder on everyone than a planned engagement that starts in the fall.
What a proper WCAG 2.1 AA process looks like: an audit against the full criterion set, a prioritized remediation plan, developer implementation, and a re-test pass before the deadline. On a mature WordPress site with legacy content, plugins of varying age, and PDFs in the media library, that sequence takes time — and the PDFs alone are often a project inside the project.
The extension is a courtesy. Institutions that use it as a planning window will be fine. Institutions that treat it as a second shrug will face the same deadline in worse shape. We’d rather have the conversation now, when there’s room to do the work right.