The Federal Government Just Set a Deadline for Your City's Website. Most Won't Make It.

In April 2024, the Department of Justice finalized a rule that most city administrators still haven't heard about. Starting April 24, 2026, every state and local government entity serving a population of 50,000 or more must have a website that meets WCAG 2.1 Level AA accessibility standards. Smaller municipalities and special districts get until April 26, 2027.

That first deadline is about seven weeks away. And based on what I've seen auditing government websites over the past 20 years, the vast majority aren't close to ready.

This is a federal requirement under ADA Title II, and the penalties for non-compliance run up to $150,000 per violation.

What the rule actually requires

The new ADA Title II web accessibility rule doesn't leave much room for interpretation. Government websites, mobile apps, and digital documents must conform to the Web Content Accessibility Guidelines (WCAG) version 2.1 at Level AA. That standard covers 50 specific success criteria across four principles: perceivable, operable, understandable, and robust.

In plain terms, here's what that means for a typical city website:

• Every image needs descriptive alt text (not "IMG_4032.jpg")
• All video content needs accurate captions
• Forms must be navigable by keyboard alone
• Color contrast ratios must meet minimum thresholds (4.5:1 for normal text, 3:1 for large text)
• PDFs posted on the site must also be accessible (this one catches almost everyone)
• Third-party widgets and embedded content you didn't build? Still your responsibility

That last point is where it gets expensive. If your city uses a third-party system for utility bill payments, meeting agendas, or permit applications, and that system fails accessibility standards, the city is still liable.

Why most municipal websites will fail

I've been building websites since the late '90s and have audited more government sites than I can count. I keep seeing the same pattern.

The site was built 8 to 12 years ago. Someone on staff picked a vendor, the vendor delivered a WordPress or Drupal site, and nobody has touched the underlying code since. Content gets updated, but nobody has reviewed the structure, the templates, the forms or the document libraries.

PDFs are everywhere. City council minutes, budget documents, zoning maps, permit applications: government sites love PDFs. Most of those PDFs were scanned from paper or exported from Word without any accessibility markup. A screen reader can't parse them. Under the new rule, every single one needs to be remediated or replaced with an accessible alternative.

Nobody on staff knows what WCAG is. I don't say that as a criticism. Municipal IT departments are stretched thin, juggling email systems, security patches and network infrastructure. Web accessibility expertise is specialized, and most cities with populations under 100,000 don't have anyone on staff who's worked with WCAG before.

Overlay widgets won't save you. Companies like accessiBe sell JavaScript widgets that claim to make your site ADA compliant with one line of code. The FTC ordered accessiBe to pay $1 million in 2025 for misleading claims about their product. Overlays do not achieve WCAG conformance. The DOJ has explicitly stated that overlays alone are insufficient. If your city installed one of these and called it done, you're exposed.

What compliance actually looks like

Real ADA compliance for a government website is a project. You can't buy it off the shelf. The process typically involves six steps:

1. Full accessibility audit. A manual review of every template, form, interactive element, and content type on the site. Automated scanners catch about 30% of issues. The rest require human testing, including keyboard navigation and screen reader testing with tools like NVDA and VoiceOver.

2. Document remediation. Every public-facing PDF needs to be checked and either remediated with proper tags, headings, and reading order, or converted to accessible HTML. For a city with 500+ documents, this alone can take weeks.

3. Template and theme fixes. The site's underlying code needs to produce accessible markup. That means proper heading hierarchy, ARIA labels where needed, focus management for interactive components, and semantic HTML throughout.

4. Third-party vendor review. Every embedded system needs to be evaluated. If a vendor's product doesn't meet WCAG 2.1 AA, you need to either get them to fix it or find an alternative. Utility payment portals, agenda management systems, and GIS mapping tools are common failure points.

5. Staff training. Anyone who adds content to the site needs to know how to add alt text, create accessible documents, and use the CMS in a way that maintains compliance. Otherwise, the site degrades within months.

6. Ongoing monitoring. You don't fix compliance once and walk away. New content, new features, and CMS updates can introduce accessibility regressions. Regular automated scans combined with periodic manual audits are the only way to stay compliant.

The cost of doing nothing

The financial exposure is real. Federal penalties under ADA Title II can reach $75,000 for a first violation and $150,000 for subsequent violations. The lawsuits hurt more.

ADA website lawsuits hit 2,014 in just the first half of 2025, a 37% increase over 2024. Those suits mostly targeted private businesses. Once the April 2026 government deadline passes, plaintiff attorneys will have a clear, codified standard to measure government sites against. Municipalities that haven't acted will be easy targets.

There's also a practical problem. Residents who can't use your website can't access your services. They can't pay their water bill online. They can't find the agenda for next week's city council meeting. They can't apply for a building permit. For residents with visual impairments, motor disabilities, or cognitive differences, an inaccessible city website is a locked door to their own government.

What cities should do right now

If you're a city administrator, clerk, or IT director reading this and realizing your website isn't ready, this is the honest priority list:

If your population is 50,000+: You have until April 24, 2026. You probably can't achieve full compliance in seven weeks if you're starting from zero. But you can demonstrate good faith by commissioning an audit, documenting a remediation plan with timelines, and starting on the highest-impact fixes (navigation, forms, top-trafficked pages). Good faith effort matters in enforcement actions.

If your population is under 50,000: You have until April 26, 2027. That sounds like plenty of time, but government procurement cycles are slow. If you need to go through an RFP process, budget approval, and vendor selection, starting now gives you a realistic timeline.

For everyone: Get an independent accessibility audit from someone who will give you an honest assessment and a clear remediation plan. Skip the vendor who built your current site (they'll undercount the issues) and any company selling an overlay product (they'll tell you the overlay is enough).

The bigger picture: your website is your front door

The ADA deadline is forcing a conversation that should have happened years ago. On top of being inaccessible, most municipal websites are outdated and confusing for everyone, including people without disabilities.

Take a city website built in 2014 on a Drupal 7 installation that hasn't been updated in three years. That's an accessibility problem, and it's also a security, usability and trust problem. When residents visit your site and see broken layouts, missing pages, and forms that don't work on a phone, they draw conclusions about how their city operates.

The ADA compliance deadline might be the push your municipality needs to modernize properly. Another overlay band-aid or a quick theme swap won't do it. A careful rebuild will, one that makes the site actually work for the people you serve.