Government websites just got another year on WCAG. That is not a reprieve
In April the Justice Department pushed its Title II web accessibility deadlines back twelve months. The standard did not move and the work did not shrink — so the agencies reading the extension as a pause are the ones most likely to miss it.
August 19, 2026
2 minutes
What the rule requires
For years a government website had to be accessible in principle, but no regulation tied that duty to a specific technical yardstick. The Justice Department’s 2024 rule under Title II of the ADA supplied one: WCAG 2.1 Level AA, applied to the web content and mobile apps that state and local governments offer the public.
That is the part worth holding onto through all the noise about dates. The standard is settled. "Accessible enough" now means something you can test a page against, criterion by criterion.
The dates moved once already
The original rule set two deadlines by population. Governments serving 50,000 people or more had until April 24, 2026; smaller governments and special-purpose districts had until April 26, 2027. Then, in April 2026, the Department issued an interim final rule that pushed both back a full year — to April 26, 2027 for the larger entities and April 26, 2028 for everyone else.
Only the calendar changed; the technical standard did not. So if you filed this under "handled" the day the extension landed, the honest status is that you bought time, not that the requirement got easier.
Who it reaches beyond city hall
Title II is broader than municipal home pages. Public universities and community colleges, public libraries, transit agencies, school districts, and community services boards all sit inside it. So do the agencies and contractors who build and maintain those sites: the obligation rides through the contract to whoever ships the code.
If your work touches a public institution, in other words, its deadline is your deadline — even where the word "government" appears nowhere on your own letterhead.
Why the extra year is easy to waste
Remediating a real government site is not a sprint you run the month before a deadline. There is an inventory to build first, and it always turns up more than anyone expected: years of untagged PDF agendas and forms, embedded payment and mapping tools that arrive with their own defects, meeting video with no captions. Then come the actual fixes, in the code, tested with the screen readers and keyboards people really use — not a scanner’s summary.
A team that starts now finishes with room to spare. A team that treats April 2027 as far off tends to discover, somewhere around month eleven, that the PDF library alone is a quarter’s work. We take public-sector clients through the same sequence we use everywhere: inventory, audit with assistive technology, fix, document in a VPAT, keep it current. The plain-language groundwork is in website ADA compliance: a plain guide for businesses.