The federal deadline every small-town website now has — and what it actually requires

If you're a mayor, city clerk, or county judge, your website picked up a federal deadline recently, and there's a decent chance nobody told you. In April 2024 the Department of Justice finalized a rule under Title II of the Americans with Disabilities Act that sets a specific technical standard — WCAG 2.1 Level AA — for the websites of every state and local government in the country. Not guidance, not a best practice: a regulation, with dates.

We've scanned more than 800 city, town, and county websites across Arkansas and Missouri against that standard. About two percent pass. This post is what I'd want to know if I were on the other side of that scan.

The dates and who they apply to

April 26, 2027 — governments serving 50,000 or more people.
April 26, 2028 — governments under 50,000, and special districts (water, sewer, fire, library, road).

Size gets you more time, not an exemption. A village of 400 with a Facebook-plus-one-page setup and a county of 45,000 running a big vendor CMS are both covered. (The DOJ extended these dates by one year in April 2026 — the standard itself didn't change.)

What WCAG 2.1 AA actually means

The Web Content Accessibility Guidelines are a set of concrete, testable requirements. The ones small-government sites fail most often, in plain terms:

Contrast — text must be readable against its background. Light gray on white fails.
Keyboard access — every menu, form, and button must work without a mouse.
Screen-reader structure — real headings, labeled form fields, and image descriptions, so a blind resident hears the page instead of gibberish.
Documents — the agendas, minutes, and forms residents actually use have to be accessible too. A scanned-image PDF of the meeting minutes is invisible to a screen reader.

None of this is exotic. It's the difference between a site built correctly and a site assembled in a template builder ten years ago and patched ever since.

What enforcement really looks like

Most of what's written about this online is fear-mongering, so let's be precise. Title II is not enforced with the $75,000 flat fines you may have seen quoted — those belong to a different part of the ADA. Enforcement comes two ways: DOJ complaints and investigations, and private lawsuits in federal court, which typically end with a consent decree requiring you to fix the site — on the court's timeline, not yours — plus the other side's attorney's fees.

So no, there isn't a six-figure penalty waiting on April 27, 2028. There is something more mundane and more expensive: being forced to do the same remediation you could have planned for, under legal pressure, with lawyers billing on both sides.

The "one line of code" email is a trap

Every clerk in America is getting emails promising instant ADA compliance from an overlay widget — a script you paste into your existing site. They don't work. The widget sits on top of the broken code without fixing it; audits still fail; sites running overlays still get sued (thousands of them have been). The DOJ's own guidance and the disability community have been blunt about this. If a vendor's pitch is "compliance without changing your website," that's the tell.

What a sensible path looks like

Find out where you stand. An automated WCAG scan takes minutes and tells you exactly what's failing and how badly. (We run these free for any city, county, or district — request one here.)
Fix the foundation, not the symptoms. If your site fails badly, remediating a rented template is usually more expensive than rebuilding on something accessible by construction — and you end that project owning your site instead of renting it.
Handle documents deliberately. Current agendas, minutes, and forms need to be accessible; decades of archived PDFs mostly don't. Publishing recurring documents as web pages instead of PDFs is cheaper and more accessible.
Keep it compliant. Accessibility isn't a one-time certificate. Whoever maintains your site should be re-auditing it as content changes.

The towns that handle this well will treat the deadline as the excuse to finally replace a site nobody likes anyway. The ones that handle it badly will pay twice — once for the widget, and once for the rebuild after the widget didn't work.

RedCyfer builds accessible municipal websites on our own government CMS, audited to WCAG 2.1 AA — see a live demonstration city or get a free accessibility scan of your site.