ADA compliance for municipal websites is now a federal requirement with firm deadlines. This plain-English guide covers what Wisconsin local governments must fix and how to get there; the official guidance lives at ADA.gov.
Key takeaways
- The Department of Justice finalized a rule requiring state and local government websites to meet WCAG 2.1 Level AA.
- Compliance deadlines depend on population size, so Wisconsin municipalities should be planning now, not after a complaint.
- Most fixes are practical: contrast, keyboard navigation, labeled forms, alt text, and accessible documents.
- Building accessibility into a redesign is far cheaper than remediating an old site page by page.
What does ADA compliance mean for a municipal website?
It means residents with disabilities can use your website with the same independence as anyone else: a screen reader can read it, a keyboard can navigate it, forms are labeled, videos are captioned, and text has enough contrast to read. The measuring stick is the Web Content Accessibility Guidelines, known as WCAG, published by the W3C.
Is web accessibility legally required for Wisconsin local governments?
Yes. Title II of the Americans with Disabilities Act applies to state and local governments, and the DOJ web accessibility rule sets WCAG 2.1 Level AA as the technical standard, with compliance dates tied to population size. Waiting for a demand letter is the expensive way to find out.
What are the most common accessibility problems on town and village sites?
The same short list shows up almost everywhere: low-contrast text on photos, menus that only work with a mouse, unlabeled contact forms, images with no alt text, links that just say click here, and minutes posted as scanned image PDFs a screen reader cannot read. Each has a straightforward fix when the site is built with accessibility in mind.
- Use real text over images, with strong contrast
- Make every menu and form usable by keyboard alone
- Give images meaningful alt text and documents real text layers
- Write descriptive link text so destinations are clear out of context
How do scanned PDFs fit into compliance?
A scanned agenda is a photograph of words, and assistive technology cannot read a photograph. Going forward, export agendas and minutes to tagged PDFs or post them as web pages. For archives, prioritize remediating the documents residents actually request instead of paying to fix decades of files nobody opens.
How do we get compliant without starting from scratch?
Sometimes you do not need a rebuild, just focused fixes. But if your site is a decade old, a redesign that bakes in accessibility usually costs less than patching, and you get a modern site out of it. Our municipal website work builds to WCAG from the first mockup, and our design team can audit your current site and tell you honestly which path is cheaper.
What does WCAG 2.1 Level AA actually ask for?
The guidelines organize into four principles: content must be perceivable, operable, understandable, and robust. In practice that means text alternatives for images, captions for video, contrast ratios of at least 4.5 to 1 for normal text, everything reachable by keyboard, no keyboard traps, clear page titles and headings, labels on every form field, error messages that say what went wrong, and code that assistive technologies can parse. None of it is exotic; it is disciplined, standard web work.
How do we test our current site?
Start with a quick pass anyone can do: unplug the mouse and try to use the site by keyboard alone, run a free checker like WAVE or Lighthouse on your top ten pages, and open a recent agenda PDF and try selecting its text. Automated tools catch perhaps a third of issues, so follow with a human review of forms, menus, and documents. Keep the results; a documented testing routine is itself evidence of good-faith effort. We include this review in every municipal project we take on, and our design team can run it on a site we did not build.
Frequently asked questions
Does the ADA rule apply to small townships?
Yes. Smaller populations get later compliance dates under the DOJ rule, but the obligation applies to public entities regardless of size.
Are accessibility overlay widgets enough?
No. Overlay toolbars do not fix the underlying code, and sites using them still receive complaints. Real conformance lives in the site structure itself.
What about third-party services like payment portals?
Your obligations extend to services you direct residents to use, so accessibility belongs in your vendor requirements when you choose payment and form providers.
How do we prove we are compliant?
Keep an accessibility statement, test results, and a remediation log. Documented, good-faith conformance work matters if a question ever arises.
Get ahead of the deadline
We build ADA-conscious government websites across Wisconsin and can review your current site in plain language. Request a free evaluation and know where you stand before the rule requires it.


