The ADA Title II web deadline moved to 2027 — what to do with the extra year

If you run communications for a public college, a city, or a county, the date you had circled has moved. On April 20, 2026 the Department of Justice published an interim final rule in the Federal Register pushing the ADA Title II web accessibility compliance dates back by a year: April 26, 2027 for entities serving populations of 50,000 or more, and April 26, 2028 for everyone else.

The short version of what to do about it: treat this as a year of runway, not a year off. DOJ said in the rule that it "fully anticipates implementing the regulation at the new deadline," and the extension is already being challenged in court.

What actually changed — and what didn’t

Only the dates moved. The rule itself, issued in April 2024, is intact, and the technical standard is unchanged: WCAG 2.1 Level AA. It still covers web pages, online forms, electronic documents like PDFs, and multimedia — which in practice means your whole digital footprint, not just the main site. DOJ’s own first-steps guidance on ada.gov is still the plainest description of the obligation.

If the alphabet soup is new to you, our plain-English guide to ADA, WCAG and the EAA covers how the pieces fit together. The pattern is familiar from Europe, too: the European Accessibility Act’s first year of enforcement showed that a deadline arriving is not the same as enforcement arriving, but also that organizations who waited for the second one had a bad time.

The extra year might not be a full year

On May 21, 2026, the National Federation of the Blind sued over the delay, arguing the agencies skipped the required public notice-and-comment period without good cause and didn’t seriously weigh the cost to disabled people. That case is unresolved. If the extension is vacated, the original date comes back, and nobody gets a fresh year to prepare.

We’re describing public reporting, not giving legal advice — your counsel’s reading of your own obligations is the one that matters.

Where images fit into this

WCAG 2.1 Level AA conformance includes the Level A criteria beneath it, and the very first of those is non-text content: every meaningful image needs a text alternative. For a campus or city team that publishes daily, images are usually the largest single category of unmet criteria, simply because there are so many of them and each one needs a human decision. Not every image needs a description, though — knowing when to write nothing is half the job.

The other half is writing something worth reading:

What to do with twelve months

Backlog and inflow are two different problems, and the year is best spent on both at once. For the backlog, work newest-first and stop at a date you choose rather than trying to fix everything — our walkthrough of auditing a year of past posts covers how to scope that without it swallowing a semester.

For inflow, the goal is that nothing new is published undescribed after a date you set — ideally this fall, while volume is already high and the habit has something to attach to. Our list of what campus teams fix before move-in week is a reasonable starting checklist. Higher-ed teams juggling program pages, news, and four social accounts can also see how SnipAlt fits a campus workflow.

A year sounds generous right up until you divide it by the number of images your team publishes in a week. Start with the inflow — it’s the only part of the pile that keeps growing while you decide.