The Title II Deadline Moved. Here's What Didn't.

ClearPath Team · 2026-09-29 · 6 min read

If you build websites for a town, a county, a school district or a library, April 24, 2026 was probably circled on somebody's calendar. That was the date the Department of Justice's Title II web accessibility rule was supposed to start applying to the largest public entities. Four days before it arrived, the DOJ moved it.

On April 20, 2026 the department published an interim final rule that pushes every compliance date back by a year. It's a genuine reprieve. It's also easy to misread, and a lot of the conversations we've seen since then treat it as a reason to shelve the project. That would be a mistake.

What actually changed

The rule itself dates back to April 2024. It says state and local government web content and mobile apps have to meet WCAG 2.1 Level AA. The only thing the April 2026 update changed is timing:

• Public entities serving 50,000 people or more now have until April 26, 2027, instead of April 24, 2026.
• Entities serving fewer than 50,000 people, and special district governments, now have until April 26, 2028, instead of April 26, 2027.

The DOJ's stated reasons were practical ones: tight budgets, thin staffing, remediation tools that turned out slower than hoped (the department specifically called out the limits of generative AI for fixing content), and the litigation risk entities faced if they missed the original date.

What didn't change

This is the part worth reading twice.

The standard is the same. It's still WCAG 2.1 AA. Nobody got a lighter version of the rule, just more time to meet it.

The exceptions are the same, and they're still narrow. Archived content, pre-existing electronic documents like old PDFs, content posted by unaffiliated third parties, individualized password-protected documents, and pre-existing social media posts. That's about it. Your event calendar, your permit forms, your bill-pay portal and every new PDF you upload are all in scope.

The ADA itself didn't move. Title II has required public entities to communicate effectively with people with disabilities since 1990. The 2024 rule gave that duty a precise technical yardstick; the extension delays when DOJ will hold people to that yardstick. It doesn't switch off the underlying obligation, and a resident who can't renew a permit because the form won't work with a screen reader doesn't have to wait until 2027 to file a complaint.

Other deadlines kept running. Healthcare organizations that receive HHS funding had their own Section 504 web deadline of May 11, 2026, and that one wasn't part of the DOJ extension. If your public client runs a hospital, a clinic or a health department, check which rule applies to which site.

Why a year goes faster than it looks

A year sounds like plenty. On a public sector timeline it often isn't. Budgets get set months ahead. Procurement for an audit or a new CMS can take a quarter by itself. Content lives across departments that each have their own web editor, and the parks department's PDF habit is not going to fix itself.

The entities that treated April 2026 as a hard stop are now a year ahead. The ones that were waiting to see what happened are exactly where they were, minus some urgency. For agencies, that second group is the one to worry about, because when 2027 gets close, they'll all call at once.

How to use the extra time well

If you look after sites for public clients, here's a sensible order of work:

1. Inventory first. List every site, subdomain, portal and app the entity runs, including the ones a vendor hosts. You can't plan remediation for a site nobody remembers owning.
2. Test the services, not just the homepage. Pay a bill, apply for a permit, register for a program, report a pothole. Do each one with a keyboard only and with a screen reader. These tasks are where residents get stuck and where complaints come from.
3. Stop the bleeding on new content. Every new inaccessible PDF or unlabeled form is future remediation work. Train the people who publish. It's cheaper than fixing their output forever.
4. Put vendors on the hook. Third-party payment and scheduling tools that the entity contracts for are not covered by the third-party exception. Ask vendors for an accessibility conformance report and put WCAG 2.1 AA in the contract.
5. Publish a way to ask for help. An accessibility statement with a real contact route doesn't satisfy the rule on its own, but it gives residents a path other than a complaint, and it shows you're paying attention.

That last step is one of the places ClearPath can take work off an agency's plate. It generates an accessibility statement from a live scan of the site, so the document reflects what's actually there rather than a template someone filled in two years ago.

What a widget can and can't do here

We'll be straight about this, because public entities get pitched a lot of overlays right now. A visitor-facing tool can make a real difference to how a resident experiences the site today: larger text, stronger contrast, a reading guide, spacing that makes a dense council agenda readable. ClearPath gives visitors those adjustments from one line of code. What no widget can do is make an inaccessible form accessible, rebuild a broken date picker, or fix a scanned PDF that has no text layer. Those are code and document problems, and the rule is going to be measured against the code and the documents.

The extension is a gift of time, not a change of direction. The entities that spend 2026 inventorying, testing and training will reach April 2027 calmly. The ones that spend it waiting will reach it the same way they almost reached April 2026.