DOJ Title II Web Accessibility Deadline Just Passed: A 12-Month Roadmap for Small Public Entities

On April 24, 2026, a deadline that had been sitting on calendars for two years arrived. State and local government entities serving populations of 50,000 or more were required to be in compliance with the Department of Justice's Title II web accessibility rule. Their public-facing websites, mobile apps, and digital services had to conform to WCAG 2.1 Level AA.

For the larger end of the public sector — big-city governments, large university systems, major county agencies — that deadline is now in the rearview mirror, with all the work, the late nights, the vendor scrambles, and the occasional missed-it-by-this-much that any major compliance deadline carries with it.

But for everyone else — small cities, towns, public school districts, public libraries, community colleges, special districts, and most state agencies serving smaller populations — the clock is now running on the second deadline:

April 24, 2027. Public entities serving fewer than 50,000 people, and most special-purpose districts, must meet WCAG 2.1 Level AA by that date.

That's roughly 11 months from publication of this post. It sounds like a long time. It isn't, especially for organizations that haven't started.

This post is for the people on that countdown. Here's what the rule actually says, who it actually applies to, and a quarter-by-quarter roadmap to get there with time to spare.

What the rule actually requires

The DOJ's final rule under Title II of the ADA — formally titled "Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities" — was published April 24, 2024.

Two things to know up front.

First, the technical standard is WCAG 2.1 Level AA. Not 2.0. Not 2.2. Specifically 2.1, at the AA conformance level. If you want a primer on what WCAG 2.1 AA actually entails as a set of testable success criteria, our WCAG 2.1 guide for web development teams walks through all of it. The good news: if you've been working toward WCAG 2.2 AA (the current standard), you already exceed the rule. WCAG 2.2 is a superset.

Second, the rule covers more than your website. Web content and mobile applications are explicitly in scope. PDFs and other documents you publish on those properties are in scope. Third-party content that you embed into your sites — chat widgets, maps, video players — is generally in scope when it's central to the program or service you're delivering.

What's not in scope (with limits): pre-existing archived content that isn't currently needed, password-protected internal employee content (covered separately under Title I), and certain third-party content that your entity didn't post and doesn't control.

The full picture, including overlap with Section 508 for federal-procurement-adjacent work, lives in our 2026 compliance timeline post.

Who's affected by the April 24, 2027 deadline

If you work for any of the following and your jurisdiction serves fewer than 50,000 people, the 2027 deadline is yours:

Cities, towns, and villages with population under 50,000
County governments for counties with population under 50,000
Public school districts for districts serving fewer than 50,000 residents
Public libraries operating in jurisdictions under 50,000
Community colleges and public technical colleges in smaller jurisdictions
Special-purpose districts of most kinds (water, sewer, fire protection, mosquito abatement, transit authorities serving small areas) — these are generally treated as falling under the 2027 deadline, though there are nuances worth confirming with counsel
Public hospitals and clinics operated by smaller local governments
Most state agencies serving public functions where the served population is under 50,000

If you're not sure which bucket you're in — particularly if you're a special district or a multi-jurisdiction entity — talk to your legal counsel. The 50,000 threshold has some edge cases.

The 12-month roadmap

Here's a realistic quarter-by-quarter plan for a small public entity starting from a near-zero accessibility baseline. If you're further along, skip ahead.

Q3 2026 (June – August): Assess and inventory

You can't fix what you don't know about. The first quarter is about taking stock.

Run a baseline accessibility audit on every public-facing property: main website, any subdomain sites, your mobile app(s), your meeting-portal or e-gov portal. Don't rely on a single-page scan — a full-site audit is essential because the issues are not evenly distributed.
Inventory your PDF and document library. Most public entities have hundreds to thousands of PDFs accumulated over years — meeting minutes, ordinances, forms, public notices. Identify which are still operationally needed (those need to be remediated) versus archival.
Inventory third-party embeds. Note every map widget, chat tool, video player, payment portal, and form tool you embed. Each vendor will need to be assessed.
Identify your accessibility coordinator. Under the rule, you should have a named person or office accountable for accessibility. This is often the existing ADA coordinator, but not always.

By end of Q3, you should have: an audit report, a document inventory, a vendor inventory, and a named accountable person.

Q4 2026 (September – November): Procurement, training, vendor pressure

This is where most entities make their biggest mistakes. You can't fix everything yourself, and you don't have to. But you do have to procure smartly.

Update your procurement language. Every contract you sign with a web vendor, software provider, or document creator from this point forward should include WCAG 2.1 AA conformance language. Don't wait until 2027 to add this — the contracts you sign this quarter will still be active in 2027.
Pressure existing vendors. If you're paying for a website CMS, a mobile app platform, or a third-party service that's central to your public mission, ask the vendor — in writing — for their plan to support WCAG 2.1 AA conformance by April 2027. Their response (or non-response) tells you which vendors to plan around.
Train your content creators. The biggest source of new accessibility issues on most public-entity sites isn't the templates or the platform — it's the day-to-day content uploads. Communications staff, clerks publishing meeting minutes, librarians posting program listings: anyone who touches the content needs basic accessibility training. Two hours is enough to cover image alt text, descriptive headings, link text, and PDF basics.
Pick a remediation tool or partner. This is where AllAccessible and similar tools fit. A budget-friendly accessibility widget paired with an accessibility statement doesn't fully replace remediation work, but it gives you a coverage layer while the remediation work is in progress.

Q1 2027 (December 2026 – February 2027): Remediate

This is the work-quarter. By now you have an audit, an inventory, trained content creators, and procurement language. Time to fix things.

Prioritize by use and severity. The pages and documents that get the most traffic (your homepage, your forms, your contact pages, your most-downloaded ordinances) come first. The 80/20 rule is brutal here — typically 20% of your content drives 80% of accessibility-relevant traffic. Fix that 20% first.
Set realistic remediation cadence. A small public entity can typically remediate 20-50 pages per week with dedicated effort, plus 10-30 PDFs. Plan accordingly.
Document everything. Every remediation gets a brief note: what was wrong, what was fixed, when. This both helps you track progress and supports any future enforcement inquiry by showing good-faith effort.
Publish your accessibility statement. It's not required by the rule, but it's strong evidence of good faith and helps users with disabilities reach you when they encounter problems.

Q2 2027 (March – April 2027): Verify and certify

The last quarter is about confirming what you've done and demonstrating it.

Run a final third-party audit. Internal audits are necessary but not sufficient. A third-party audit — by an independent accessibility consultancy, by your vendor's professional services team, or by an automated tool combined with manual review — gives you independent verification.
Test with assistive technology users. Wherever possible, have an actual screen-reader user, keyboard-only user, or low-vision user navigate your most important workflows. Studies from WebAIM and similar researchers suggest automated tools catch roughly a third of WCAG issues; the rest require human testing.
Establish ongoing monitoring. Accessibility is not a one-time project. Set up a quarterly re-audit cadence, monthly content-creator refreshers, and an ongoing process for handling user-reported accessibility issues.
Document your conformance posture. Internally, have a current "where are we" report ready in case of inquiry. Externally, keep your accessibility statement updated.

Common pitfalls and misconceptions

In the months since the large-entity deadline, we've seen a few patterns from public entities that struggled. Here are the most common.

Pitfall 1: Treating the deadline as a single project. WCAG 2.1 AA conformance is not a milestone you cross and then ignore. New content goes up every day. Vendors change features. Browsers evolve. Without an ongoing process, your conformance posture decays the day after you "finish."

Pitfall 2: Buying a widget and calling it done. A good accessibility widget — including ours — is a useful coverage layer. It is not a substitute for fixing the underlying content. DOJ guidance has consistently warned that overlay tools alone are not a substitute for remediation. Use widgets for what they do well (toolbars, contrast adjustments, screen-reader assistance for users who don't have their own AT). Use remediation for what it does well (actually fixing the source content).

Pitfall 3: Ignoring PDFs. Most public entities have legacy PDF problems that dwarf their web-content problems. Inaccessible meeting minutes, inaccessible forms, inaccessible budget documents. Plan PDF remediation as an explicit workstream, with its own timeline and budget.

Pitfall 4: Assuming third-party tools are someone else's problem. If you embed a third-party tool and it's central to delivering your public service, it is your problem under the rule. Pressure your vendors. If they won't conform, replace them. There's still time, but only if you start now.

Pitfall 5: No accessibility coordinator. "Everybody's job" is nobody's job. The entities that struggled most were the ones where accessibility was a shared concern with no single accountable owner. Pick a person. Empower them. Make it part of their formal job description.

How AllAccessible fits in

We make accessibility tooling for organizations including small public entities. A few specific ways we help with this deadline:

Full-site accessibility audits that show you where you stand against WCAG 2.1 AA and WCAG 2.2 AA — not just your homepage, every page.
Per-page remediation through our widget, including human-in-the-loop agentic AI remediation where AllAccessible agents propose accessible labels and your team approves before anything goes live.
Public-entity-friendly pricing including à-la-carte addons so smaller entities aren't forced into enterprise plans. Start a 7-day trial — no credit card required.
Accessibility statement templates and compliance reporting suitable for government use.

We're not the only option, and we don't claim to make you "ADA compliant" — compliance is a legal posture only your attorney can attest to. We are a useful and budget-friendly part of a serious accessibility program.

What to do this week

If you take only one action after reading this:

Run a free audit on your main public-facing site. Start here. It takes about ten minutes and gives you a baseline.
Forward this post to whoever in your entity handles ADA, IT, or communications, so you have the conversation on the calendar.

Eleven months sounds like a lot. The entities that hit their deadline in April 2026 will tell you it isn't. Start this quarter.