The deadline moved and that's worse news than it sounds

On April 20, 2026, the Department of Justice issued an interim final rule pushing the Title II web accessibility compliance dates back one year. Public entities serving 50,000 or more people now have until April 26, 2027. Smaller entities and special district governments have until April 26, 2028. Nothing about the requirements changed. The standard is still WCAG 2.1 Level AA.

That is 245 days from today for the first group.

I said last Monday I'd lay out what the rule requires and a realistic sequence for getting there. But first, I think the extension changed how everyone is reading this.

What actually changed in April 2026? Two dates. That’s the entire substantive content of the interim final rule.

The standard, the scope, the conformance level, stayed the same. We’re still talking about WCAG 2.1 Level AA, applied to web content and mobile apps that a public entity provides or makes available.

One more date that did not move, and I completely missed this. HHS kept a separate Section 504 web accessibility deadline of May 11, 2026 for organizations receiving HHS funding.

The DOJ said public entities lack the technical expertise and the funds to comply, and it said, that generative AI cannot reliably automate accessibility remediation at scale.

Sit with the second one for a second. The federal government looked at the state of automated remediation, including every AI overlay and one-line-of-JavaScript vendor currently in your inbox, and concluded it does not work well enough to count on.

The DOJ also signaled it intends further rulemaking on the substantive requirements. Translation: the target may get more specific, not less.

Here is the practical problem with a one-year extension. Accessibility work is not a thing you do in the last quarter. It is a thing that either lives in your templates, your CMS, your procurement, and your editor training, or it does not live anywhere. An extra year spent not building those four things produces exactly the same site you had in April, plus twelve months of new content built the old way.

I have watched this exact pattern for more than twenty years in higher education.

It does not mean a scanner gave you a 94. Conformance under WCAG 2.1 AA means every success criterion is met on every page in scope, for the full content of that page, including the parts your CMS renders from a third party. There is no partial credit and no scoring curve. A page either conforms or it does not.

Three things people consistently misjudge:

Automated tools find roughly a third of it. That is the honest number, and it is generous. Contrast, missing alt attributes, form fields without labels, obvious heading skips, and duplicate IDs are machine-checkable. Whether your alt text is correct, whether your heading structure describes the actual document, whether a keyboard user can complete a task, whether your error messages make sense in a screen reader, whether your video captions are accurate: none of that is machine-checkable. It requires a person.

PDFs count. If it is on your site and a member of the public needs it, it is in scope. The rule has narrow exceptions, and "we have a lot of them" is not one.

Third-party embeds count. Your maps, your video players, your payment forms, your event calendars, your chatbot. If you put it on your page, it is your page.

If you are in the April 2027 group, you have eight working months. Here is the order I would run them in, and the order matters more than the speed.

Because a 500-page site is not 500 problems. It is usually eight to twelve problems, repeated.

Your header, your footer, your navigation, your card grid, your accordion, your table style, your form components, your breadcrumbs. Fix the heading order in one template and you have fixed it on every page that uses it. Fix the focus indicator once and every keyboard user on the site benefits.

This is why I always tell people to spend two months on templates and one week on individual pages, and never the other way around. Page-by-page remediation is how organizations spend an entire budget and end up with a site that fails the same way it did before, just in different places.

The corollary is uncomfortable: if your templates come from a vendor theme you cannot edit, your remediation project is actually a platform project, and you should find that out in September rather than March.

Below is a worked example, not a quote. The volumes are made up. Substitute your own from step one.

Two things about that table. First, the PDF row is where budgets die. Second, none of it is a one-time cost, because next year you will publish more content. The organizations that get this right stop treating accessibility as a project and start treating it as a standard, which costs less over five years and more in month one.

If you want the inventory step to take a day instead of a month, eiSEO will scan your first 100 pages free at eiSEO and hand you a sorted list of what is actually broken. That is step one of seven. It is not the answer. But you cannot triage what you have not counted, and September starts in a week.

If we start now, we can meet the deadline and if you need assistance, please let me know.

See you next Monday.