Accessibility can feel like a legal minefield full of acronyms. But at its heart it’s simple: every resident — including people using screen readers, keyboards, magnification, or captions — should be able to use their town’s website. Here’s what clerks and administrators actually need to know.
The short version
- WCAG (Web Content Accessibility Guidelines) is the technical standard most requirements point to. Current practice targets WCAG 2.2, level AA.
- ADA and related requirements increasingly apply to government websites. Requirements vary by jurisdiction and change over time, so confirm the specifics that apply to your municipality with your attorney or association.
- Accessibility is mostly built in — or it isn’t. A well-built platform handles the technical layer (structure, contrast, keyboard support, forms). Staff mainly need good habits for the content they add.
Habits that keep your content accessible
- Write descriptive link text (“Download the 2026 budget” — not “click here”).
- Add alternative text to images that carry information.
- Use real headings in order, not bold text pretending to be headings.
- Prefer web pages over scanned PDFs. When PDFs are necessary, start from a text document, not a scan.
- Keep tables for data, with header rows — not for layout.
Questions to ask any website vendor
- What WCAG version and level do you build to, and how do you test it?
- Is accessibility part of the core product or a paid add-on?
- Will the forms, menus, and documents we publish stay accessible as we edit them?
An accessible website isn’t just lower risk. It’s a better website for every resident — clearer, simpler, and easier to use on any device.