Having trouble using a website? Tell us — a person will help.

No vendor can honestly answer that with a straight yes, and you should be wary of one who does. Under Title II of the ADA the legal obligation belongs to your municipality, not to your website company, and it covers your programs and services, not only your web pages. What we can tell you is what we do. Every Town Web site is built to WCAG 2.1 Level AA, the accessibility standard the DOJ rule adopts, and worked on after launch. We also show you where your site stands. What we will not do is hand you a certificate, because no such certificate exists. Our accessibility statement sets all of this out in writing.

In practice, nothing you can rely on. There is no test that returns 100%, no federal body that certifies websites as compliant, and no vendor who can promise you the number. Automated checkers disagree with one another, and many of the requirements need human judgment: whether alt text is meaningful, whether reading order makes sense, whether a form behaves the way a screen-reader user expects. So when a company sells you a “100% ADA compliant” website, it is describing a marketing claim, not a status your board can point to. That is why you will not find the phrase anywhere on this site.

In the sense that the work gets done and you can see it. On our side: page structure, heading order, color contrast, keyboard and screen-reader navigation, forms, buttons, link text, and every template your content sits in. On our newest platform, which is rolling out now, the website accessibility tool scans your pages and documents after launch, flags any issues it finds, keeps a record of what has been found and fixed, and the editor warns you about likely problems before you publish. We check for dead links so residents do not land on a page that is gone, and when we find an accessibility problem in our own code we fix it and push the update to every site it affects. Accessibility is not a box we tick at launch, and it is never finished. More on how we work on it.

An accessible municipal website has two parts, and it matters which is which. Town Web builds and maintains the platform: the themes, templates, menus, navigation, and the tools your team works in. Your municipality owns the content it publishes: the text, images, videos, uploaded documents, and anything embedded from somewhere else. We help you with that second part, and on our newest platform the scanner flags problems in it, but the decision about what to publish, fix, or take down is yours. The accessibility statement lists the split line by line.

The Department of Justice’s Title II rule adopts WCAG 2.1 Level AA as the technical standard for state and local government web content. The compliance dates it sets are April 26, 2027 for public entities serving 50,000 or more people, and April 26, 2028 for entities serving fewer than 50,000 and for special district governments. There is real work in that, but it is a planning horizon rather than an emergency, and we are glad to help you map it out. Requirements and dates are set by federal authorities and can change, so check with your own legal counsel for what applies to your municipality.

Because many older government PDFs started life on a scanner. A scanned budget, set of minutes, or zoning plan is a picture of text as far as a screen reader is concerned, so it reads as nothing at all. Documents are the most common source of accessibility problems on a municipal site, and a site can score well on its pages and still be let down by its files. On our newest platform, our tool checks your documents for searchable text, proper tagging, and screen-reader compatibility. When one is not accessible we show you how, and we are building tools to fix them. Some legal documents cannot be rewritten at all, and for an ordinance or a signed record the practical answer is to keep the original and post a plain-language summary next to it.

Forward it to us before you reply or pay anyone. A lot of those messages are sales pitches built on a single automated scan, and no tool can declare a site non-compliant the way they suggest. We will run a scan of your site, show you what it actually says, and if there is a genuine problem we will walk you through it. You will not get a bill for that conversation.

Yes. Our accessibility statement is public, dated, and written to be handed to a board or attached to an RFP response: it names the standard we build to, what we are responsible for, what the municipality is responsible for, what our scanner does and does not do, and the limitations we know about. Alongside it, on our newest platform, the record your dashboard keeps of what has been found and fixed shows the work over time. If your board needs something more specific, ask us and we will put it together.