ADA-Compliant Websites for Wisconsin Local Governments: A Plain-English Guide
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.
How Much Does a Municipal Website Cost in Wisconsin?
Key takeaways
- Most Wisconsin municipal websites are quoted flat-rate by scope: page count, content migration, forms, payments, and accessibility work drive the price.
- Budget for the whole life of the site, including hosting, security updates, and support, not just the build.
- A clear request for proposals gets you comparable bids; a vague one gets you guesses.
- Small townships and villages can phase the work to fit a lean budget year.
What decides the cost of a municipal website in Wisconsin?
Five things drive the number: how many pages and documents the site needs, how much old content has to be migrated or rewritten, which online services you offer (payments, forms, permits), the accessibility standard you build to, and who maintains the site after launch. A five-department city site with years of minutes costs more than a township site with a dozen pages, and it should.
Why do bids for government websites vary so widely?
Because vendors are not bidding the same work. One bid assumes your staff moves the content; another includes migration, rewriting, and accessible PDF remediation. One includes training and support; another hands you the keys and leaves. Before comparing prices, compare what is actually in scope. Our guide to writing a website RFP shows how to make bids comparable.
What ongoing costs should a municipality expect?
Plan for hosting with backups and security updates, a support arrangement for changes staff cannot make, and periodic accessibility reviews as content grows. These are small line items compared to the build, and they keep the site fast, secure, and compliant. We bundle hosting, backups, and updates as one predictable annual rate so budgeting stays simple.
How can a small town keep the project affordable?
Phase it. Launch with the core: government pages, agendas and minutes, notices, contacts, and the two or three services residents use most. Add online payments, extra forms, and department microsites in a later budget year. Phasing spreads the cost without leaving residents waiting on the essentials.
- Start with the pages that answer real calls to the office
- Use your existing payment provider instead of adding a new one
- Have staff gather content early; collection delays cost more than design
What does Fox Valley Web Design charge?
Every municipality is quoted flat-rate after a free consultation, because scope varies so much between a township and a county department. You get a written proposal your board can approve with no hourly surprises, from the same municipal website team that builds and hosts government sites like the Town of Chilton.
What does a realistic municipal project budget look like?
Think in three buckets. The build covers strategy, design, development, accessibility, and training. Content work covers migrating documents, rewriting pages into plain language, and remediating key PDFs; this bucket varies most between municipalities and is where honest scoping saves money. Ongoing costs cover hosting, security updates, support time, and periodic accessibility checks. Boards that budget all three buckets up front avoid the common trap of a nice launch followed by slow decay because nobody owns maintenance.
- Build: design, development, accessibility, training
- Content: migration, rewriting, document remediation
- Ongoing: hosting, updates, support, reviews
Which features are worth paying for first?
Prioritize what reduces counter traffic and phone calls: online payments connected to your existing provider, fillable forms for the permits people actually request, a notices system the clerk can update in a minute, and a meetings hub with agendas and minutes in one place. Features like interactive GIS layers, resident portals, and mobile apps can be genuinely useful for larger communities, but for most Wisconsin towns they belong in a later phase after the fundamentals are earning their keep.
Frequently asked questions
Can a municipal website be paid across two budget years?
Yes. Phased builds are common in local government, and we structure proposals so each phase stands on its own for approval and invoicing.
Does the quote include accessibility?
Yes. Accessible structure, contrast, navigation, and forms are part of the build, not an upsell. Remediating large document archives is scoped separately so you can see the cost.
Is training included?
Yes. We train your clerk or staff to post agendas, notices, and updates, and we stay on call for anything you would rather send to us.
Do grants or shared-services funds ever cover websites?
Sometimes. Broadband, tourism, and modernization programs occasionally include web projects; check with your county and the League of Wisconsin Municipalities on current programs before budgeting.
Get a number your board can act on
Request a quote and we will scope your site in plain language: what it includes, what it costs, and what it will cost to keep running. No hourly meters, no surprises.
How to Write a Website RFP: A Guide for Wisconsin Municipalities & Organizations
Key takeaways
- A good website RFP describes outcomes and required services, not a specific design.
- Ask every vendor the same questions about accessibility, hosting, training, and support so bids are comparable.
- Require examples of similar work; a vendor who has built for government or industry can show it.
- Score total cost of ownership across several years, not just the build price.
What belongs in a website RFP?
An effective request for proposals covers eight things: who you are and who the site serves, what the current site does poorly, required features, content migration expectations, accessibility requirements, hosting and security expectations, training and support after launch, and how proposals will be scored. Keep it under ten pages; a focused RFP attracts focused bids.
Which requirements separate serious vendors from template shops?
Ask how they meet WCAG accessibility, where the site is hosted and by whom, who owns the site and content when the contract ends, what happens when you need a change at 4 p.m. on a Friday, and which comparable organizations they have built for. Vague answers to any of these predict a rough project.
- Accessibility approach, tested how, to which WCAG level
- Hosting location, backups, and security update responsibility
- Full ownership of domain, site, and content by your organization
- Named support contact and realistic response times
- Live examples of comparable work, like our client portfolio
How should proposals be scored?
Weight qualifications and fit above sticker price. A common split: forty percent relevant experience and references, twenty five percent approach and accessibility, twenty percent total five-year cost including hosting and support, fifteen percent timeline and training. The cheapest build often carries the highest lifetime cost.
What do vendors wish every RFP included?
A content honesty statement. Say plainly who is writing and gathering content, how many pages and documents exist today, and who approves things. Content is the number one cause of website delays, and bids swing widely on those assumptions. Being clear up front is how you get a number that holds; it is also why our municipal cost guide puts content migration near the top of the price drivers.
What does a workable RFP timeline look like?
A calm sequence beats a rushed one: two weeks to draft and approve the RFP, three to four weeks for vendors to respond with a written question period in the middle, one week to score and shortlist, demos with two or three finalists, then award and a kickoff four to six weeks out so content gathering can start. Publishing answers to all vendor questions keeps the process fair and the bids aligned. Total, about a quarter from draft to kickoff, which fits neatly into a municipal budget cycle.
What red flags should reviewers watch for in proposals?
Watch for proprietary platforms you cannot leave without rebuilding, hosting bundled so tightly you never own your own site, accessibility promised as a plugin rather than built work, support priced hourly with no response commitment, and portfolios full of industries nothing like yours. A trustworthy proposal names who does the work, shows comparable projects like our Town of Chilton build, and reads like the vendor already understands your organization.
- Platform lock-in and unclear ownership
- Accessibility as an afterthought
- No named support contact or response times
- No comparable work to show
Frequently asked questions
Do we have to take the lowest bid?
Usually not for professional services; most Wisconsin municipal purchasing policies let you weigh qualifications. Check your own policy and score what actually matters.
How long should vendors get to respond?
Three to four weeks is respectful and gets you thoughtful proposals. One-week turnarounds mostly collect boilerplate.
Should we require a demo?
Ask finalists to walk through one comparable live site and show its editor. Ten minutes in a real dashboard tells you more than any slide deck.
Can Fox Valley Web Design respond to our RFP?
Yes. We regularly propose on municipal, industrial, and organizational projects across Wisconsin, and we are happy to review a draft RFP and point out anything that will muddy your bids.
Send us your RFP, or let us help you write it
Whether you are a village board, a school district, or a manufacturer formalizing a redesign, we will respond with a clear, flat-rate proposal. Start here or see how we build on our website design page.
Municipal Website Design in Wisconsin: What Towns, Villages & Cities Need
Key takeaways
- A municipal website is a service counter that never closes: agendas, minutes, permits, payments, and notices should be findable in two clicks.
- Accessibility is not optional for local government sites, so plan for ADA and WCAG conformance from the start.
- Residents search Google first, which means clear page titles and plain-language content decide whether they find your hall or call it.
- Wisconsin towns and villages can get a professional, secure site without big-city agency pricing.
What should a Wisconsin municipal website do for residents?
A municipal website should let residents finish common tasks without a phone call: find meeting agendas and minutes, pay a bill, apply for a permit, report an issue, and check garbage, recycling, or snow routes. When the website handles the routine questions, staff time goes to the work that actually needs a person.
That standard applies to every size of government, from a township of a few hundred people to a county seat. The Town of Chilton website we built is a working example: services, notices, and contacts organized around what residents look for, not around departments.
What pages does a town or village website need?
Most Wisconsin municipal sites need the same core set: government (board, committees, staff), agendas and minutes, ordinances and policies, permits and licenses, public works and utilities, elections, parks, news and notices, and a contact page with office hours. Beyond the core, add what your community actually uses.
- An emergency or alert banner the clerk can turn on in seconds
- A public notices page that satisfies posting requirements
- A calendar for meetings and community events
- Forms residents can submit online instead of printing
Why does accessibility matter so much for local government?
Government services must be usable by everyone, including residents who rely on screen readers, keyboard navigation, or captions. Public entities are covered by the Americans with Disabilities Act, and the Department of Justice has published a web accessibility rule for state and local governments based on WCAG 2.1. Building to that standard from day one costs far less than fixing a site after a complaint.
We cover the details in our plain-English guide to ADA-compliant municipal websites, but the short version is: readable contrast, keyboard-friendly menus, labeled forms, alt text, and documents that are not scanned images.
How should a municipality handle agendas, minutes, and notices?
Post them as accessible pages or tagged PDFs, in one predictable place, with the newest items first and an archive by year. Residents and reporters should never have to guess where this week’s agenda lives. A consistent posting routine also builds a public record you can point to when questions come up.
Who updates the website after launch?
Your clerk or staff should be able to post a notice, update hours, or add an agenda without calling a developer. We build municipal sites on WordPress with an editor staff can learn in an afternoon, and we stay on call for the changes you would rather hand off. Hosting, backups, security updates, and support come from the same Wisconsin-based team that built the site.
How should a municipal site be organized so residents find things?
Organize by task, not by org chart. Residents think pay my water bill, reserve a shelter, when is my recycling day; they do not think Department of Administration. Group the homepage around the ten most common tasks, keep a full A to Z services index for everything else, and put a working search box in the header. Test the structure by asking someone outside the office to find three things; if they hesitate, rename the menus in plainer words.
- Homepage: top tasks, alerts, next meeting, contact hours
- One predictable home for agendas, minutes, and notices
- An A to Z index so nothing depends on guessing a department
- Search that actually searches documents as well as pages
What security does a government website need?
Local government sites are routine targets, so the basics are not optional: SSL on every page, a hosting stack that gets security updates on a schedule, offsite backups tested by restoring them, limited admin accounts with strong authentication, and a plan for who to call when something looks wrong. Our managed hosting handles updates, monitoring, and backups for the municipal sites we build, so a clerk never has to think about server patches. Ask any vendor who is responsible for security updates by name; if the answer is vague, the risk is yours.
Frequently asked questions
How long does a municipal website project take?
Most town and village sites launch in four to eight weeks, depending on how much content needs to be gathered, rewritten, and organized. Migrating years of minutes and agendas adds time, and we plan that with you up front.
Can residents pay bills or fees through the site?
Yes. We connect your site to the payment provider your municipality already uses, or help you choose one, so utility payments, permits, and licenses can be handled online.
Do you work with small townships or only cities?
We build for townships, villages, cities, sanitary districts, and county departments across Wisconsin. The structure scales down as well as up.
Is the website hosted in the United States?
Yes. Hosting is PCI-compliant, American-based cloud infrastructure with backups, monitoring, and updates handled for you.
Bring your municipal website up to what residents expect
Fox Valley Web Design builds and supports government and community websites across Wisconsin, from design and development to hosting, photography, and ongoing updates. Request a quote and we will walk your board through a clear, flat-rate proposal.
Thank you American Veterans for the freedoms we enjoy in America!
Happy Memorial Day