April 2026 WCAG Deadline: What Every Municipality Needs to Know

Who Does This Apply To?

The rule applies to every “public entity” under Title II of the ADA. This includes:

Cities and towns — every municipal website, including utilities, parks & recreation, and public works
Counties — county government portals, courts, health departments
School districts — district websites, school sites, parent portals, learning management systems
Public libraries — library websites, online catalog systems
Public universities and community colleges
Special districts — water, fire, transit, housing authorities
State agencies — all departments and divisions

What Is WCAG 2.1 AA?

WCAG stands for Web Content Accessibility Guidelines. It's the international standard for making web content accessible to people with disabilities. Level AA is the middle tier — not the bare minimum (A), not the most stringent (AAA), but the level the DOJ has determined is both achievable and meaningful.

Key requirements include:

Text alternatives — all images must have alt text describing their content
Color contrast — text must have at least a 4.5:1 contrast ratio against its background
Keyboard navigation — every function must be operable via keyboard alone
Form labels — all form fields must have associated labels
Error identification — form errors must be described in text
Consistent navigation — navigation must be consistent across pages
Resize text — content must be readable when zoomed to 200%

Two Deadlines Based on Population

The rule uses population size to determine the compliance date:

50,000+ population: April 24, 2026 — this includes most cities, large school districts, counties, and state agencies
Under 50,000 population: April 24, 2028 — small towns, small districts, and rural entities

Note: the population threshold refers to the entity's service area, not necessarily the municipality's census population. School districts serving 50,000+ students and counties with 50,000+ residents fall under the 2026 deadline.

What Happens If You're Not Compliant?

Non-compliance exposes your entity to several risks:

DOJ enforcement actions — the DOJ can investigate and enter consent decrees requiring compliance plus monetary damages
Private lawsuits — individuals can file complaints and lawsuits. ADA web accessibility lawsuits have increased 300%+ since 2018
Settlement costs — typical government accessibility settlements range from $10,000 to $75,000+, plus mandatory remediation costs and ongoing monitoring
Loss of federal funding — some federal programs condition funding on ADA compliance

What Should You Do Right Now?

1. Scan Your Website

Run a WCAG 2.1 AA compliance scan to see where you stand. Automated scanners can identify 30-50% of accessibility issues instantly — things like missing alt text, color contrast failures, and missing form labels. This gives you a baseline.

2. Document Your Findings

Generate a compliance report that catalogs every violation by severity. This document serves two purposes: it gives your IT team a fix list, and it demonstrates to your council/board that you're taking action.

3. Prioritize Fixes

Not all violations are equal. Focus on critical and serious issues first — these are the ones most likely to trigger complaints:

Missing alt text on images (most common violation)
Insufficient color contrast (affects readability)
Missing form labels (breaks assistive technology)
Keyboard traps (users get stuck and can't navigate)

4. Hand the Report to Your Web Vendor

Most government websites are maintained by a CMS vendor or contracted developer. A good compliance report includes specific code fixes they can implement — not just a list of problems.

5. Set a Remediation Timeline

With the April 24, 2026 deadline, you have limited time. A typical remediation project for a government website with 20-50 violations takes 2-6 weeks of developer time, depending on complexity.

What About Accessibility Overlays?

Some vendors sell JavaScript widgets you paste into your site that claim to fix accessibility automatically. These do not constitute compliance. The DOJ's own guidance, multiple court decisions, and the National Federation of the Blind have all stated that automated overlays are insufficient. They can actually make accessibility worse by interfering with screen readers.

The only path to compliance is fixing your actual HTML, CSS, and content — which is exactly what a compliance report helps you do.

How AccessScan Helps

We built AccessScan specifically for government entities facing this deadline. Here's what you get:

Free scan — enter your URL and see your violation count and score in 30 seconds
Professional compliance report ($49) — every violation cataloged with plain-English explanations and specific code fixes your developer can implement
Multi-page audit ($99) — scan up to 10 pages for comprehensive coverage of your site

Both plans fall under the federal micro-purchase threshold — your department head can approve this with a credit card today. No procurement process required.