ADA Title II Website Compliance: What Local Governments Need to Know in 2026

For 34 years, the ADA told state and local governments to make their digital services accessible without defining what "accessible" actually meant. That changed. The Department of Justice finalized a rule that puts a specific standard on the books: WCAG 2.1 Level AA.

If you work for a city, county, school district, public library, or any other state or local government entity, this applies to you.

What the Rule Actually Says

All public-facing digital content from state and local governments must conform to WCAG 2.1 Level AA. That includes your website, your online forms, your PDFs, your customer portals, your mobile apps, your videos, and any embedded third-party tools like chatbots, payment processors, or scheduling widgets.

In practical terms, it means your website needs sufficient color contrast, keyboard navigability, alt text on images, captions on videos, proper heading structure, accessible forms, and compatibility with assistive technologies like screen readers.

This isn't a new law. The ADA has required accessible government services since 1990. What's new is the specificity. Before this rule, "accessible" was open to interpretation. Now there's a defined standard with defined deadlines.

The Deadlines

April 24, 2026: State and local governments serving populations of 50,000 or more.

April 26, 2027: State and local governments serving populations under 50,000, plus special district governments (water districts, fire districts, transit authorities, and similar entities).

If your deadline has already passed or is approaching, don't panic. But do start.

Why This Matters Even With Enforcement Uncertainty

There is uncertainty about federal enforcement right now. The DOJ may be working on modifications to the rule.

Here's why that doesn't change what you should do: the rule is finalized and enforceable until it's officially changed. And federal enforcement was never the only risk.

Private lawsuits under Title II are expected to increase. When plaintiff attorneys look for cases, they need to prove the plaintiff was actually affected. For government services, that's straightforward. A resident trying to access public benefits, pay a utility bill, or apply for a permit has clear standing. They need these services. They're entitled to them.

The practical takeaway: make yourself a difficult target. Organizations that can show they know their issues, have a documented plan, and are actively fixing problems are significantly harder to sue successfully.

You don't have to be perfect. You have to be demonstrably trying.

What "Accessible" Looks Like in Practice

A resident who is blind can use a screen reader to navigate your site, understand every page, complete every form, and access every service.

A resident with low vision can zoom the page to 200% without content breaking or overlapping. All text meets a 4.5:1 contrast ratio against its background.

A resident who can't use a mouse can navigate every page, open every menu, complete every form, and activate every button using only a keyboard. A visible indicator shows which element is currently focused.

A resident who is deaf can understand your video content through accurate, synchronized captions.

A resident with a cognitive disability encounters clear language, consistent navigation, helpful error messages, and a predictable layout.

If any of these scenarios fail on your website right now, you have issues that need to be addressed.

Six Steps to Getting Compliant

Step 1: Know What You Have

Inventory every public-facing digital asset. Your website (all pages, not just the homepage), PDFs, online forms, customer portals, videos, mobile apps, and embedded third-party tools. Create a spreadsheet. List every asset. Assign an owner. Tag each as high, medium, or low risk.

A rough inventory now is infinitely more valuable than a perfect inventory three months from now.

Step 2: Find the Problems

Run automated scans using free tools like axe DevTools, WAVE, or Lighthouse. These catch roughly 30-40% of issues: missing alt text, color contrast failures, missing form labels, empty headings.

But automated tools miss the most important issues. Tab through your top 10 pages using only your keyboard. Can you reach every interactive element? Is there a visible focus indicator? Try navigating with a screen reader. You'll learn more from 30 minutes of hands-on testing than from reading any article about accessibility.

Document everything with screenshots and severity levels.

Step 3: Prioritize and Plan

Fix first: anything that blocks access to services. Broken forms, inaccessible logins, keyboard traps.

Fix next: issues that significantly degrade the experience. Poor contrast, missing headings, unlabeled form fields, videos without captions.

Fix systematically: issues that cause inconvenience but don't block access.

Assign each issue to a person. Set real deadlines.

Step 4: Fix What Matters

Start with your most-visited pages and your most critical forms. Some quick wins that make a big difference:

Add a visible focus indicator so keyboard users can see where they are on the page. Add a skip navigation link so keyboard users can jump past the header. Set the language attribute on your HTML element. Fix your page titles so each one is unique and descriptive. Make sure every form input has a visible, connected label.

Step 5: Train Your Team

Fixing your website today doesn't help if new inaccessible content goes live tomorrow. Everyone who creates content or updates your site needs to understand the basics: how to write good alt text, how to use headings correctly, how to create accessible documents.

Free training resources are available from WebAIM, Deque University, and the W3C.

Step 6: Make It Permanent

Run scans regularly. Include accessibility in every development process. Review new content before publishing. And maintain an accessibility statement on your website that honestly describes your current status, what you're working on, and how people can report barriers.

That statement demonstrates awareness and good faith. It gives people a way to reach you before they feel their only option is filing a complaint.

What NOT to Do

Don't buy an accessibility overlay. Those floating toolbar widgets do not achieve compliance. They don't fix the underlying issues. They can create new problems for screen reader users. They've been named in multiple lawsuits. And the National Federation of the Blind has publicly opposed them.

Don't trust vendor claims without testing. Your payment portal vendor says their product is accessible. Test it yourself. You're liable for inaccessible third-party tools on your site regardless of what the vendor's marketing says.

Don't assume you'll fix it later. Later never comes. Budget gets cut. Priorities shift. And every day your site stays inaccessible, residents are being excluded from services they need.

The Cost of Action vs. Inaction

Building an accessible website costs roughly the same as building an inaccessible one. The difference is in the expertise of the team building it.

Remediating an existing site costs more because you're paying to find and fix preventable problems. A comprehensive accessibility audit runs $500 to $5,000 depending on site size. Remediation work can run $2,000 to $20,000+.

A single ADA lawsuit, even one you win, typically costs $10,000 to $50,000 in legal fees.

The math is clear.

Getting Started Today

Pick one page on your website right now. Run the free axe DevTools extension on it. Tab through the entire page using only your keyboard. Fix one thing you find.

That's today. Tomorrow, do the next page.