Web Analytics

WCAG 2.1 AA Checklist for Small Towns: ADA Website Compliance Before 2028

WCAG 2.1 AA checklist: village clerk reviewing an accessible municipal website

If your village, town or special district serves fewer than 50,000 people, this WCAG 2.1 AA checklist is your roadmap to ADA website compliance. In April 2026 the U.S. Department of Justice moved your deadline to April 26, 2028. That sounds far away. It isn’t, if you have a part-time clerk, years of scanned PDFs, and no IT department.

This guide is written for small towns. It skips the legal theory and tells you what to check, what to fix first, and what you can safely leave alone. For the full story on the deadline change, see our post The ADA Website Deadline Moved — Your Risk Didn’t.

Who has to comply, and by when

The DOJ’s Title II rule covers every state and local government website and mobile app. That includes villages, townships, counties, school districts, park districts, library districts, fire protection districts and other special districts.

Your entity Compliance date
Population of 50,000 or more April 26, 2027
Population under 50,000 April 26, 2028
Any special district government April 26, 2028

The required standard is WCAG 2.1 Level AA. The DOJ has also asked for public comment on making the rule less costly for small governments, so more changes are possible. Don’t count on that. The underlying ADA duty to serve residents with disabilities already applies today, and complaints don’t wait for deadlines.

The WCAG 2.1 AA checklist for small municipalities

WCAG has dozens of success criteria. This WCAG 2.1 AA checklist sticks to the ten items that, in our audits of small-town websites, cover the large majority of real problems.

1. Every image has meaningful alt text

Photos of the water tower, the new park pavilion, the mayor at a ribbon cutting: each needs a short description a screen reader can read aloud. Decorative images (dividers, background patterns) should be marked as decorative so screen readers skip them.

2. Text has enough color contrast

Normal text needs a contrast ratio of at least 4.5:1 against its background. Light gray text on white and white text on pale blue banners are the most common failures we see. Free contrast checkers will tell you in seconds.

WCAG 2.1 AA checklist: keyboard navigation with a visible focus outline on a town website
Every menu, form and button should work with a keyboard alone.

3. Everything works with a keyboard

Unplug your mouse and try to pay a water bill, find a meeting agenda and submit a contact form using only the Tab and Enter keys. Menus, sliders and pop-ups that can’t be reached by keyboard are an automatic failure.

4. You can see where the keyboard focus is

As you tab through the page, a visible outline should show which link or button is selected. Many themes remove this outline because someone thought it looked untidy. Put it back.

5. Headings are in a logical order

Each page should have one main heading (H1) followed by H2 and H3 sections in order. Screen reader users jump between headings the way sighted visitors skim. Don’t pick a heading level just because you like its font size.

6. Links say where they go

“Click here” and “Read more” mean nothing when a screen reader lists all the links on a page. Use “Download the March 2027 board agenda (PDF)” instead.

7. Forms have labels and clear error messages

Every field in your FOIA request, service request and contact forms needs a visible label tied to it in code. When someone makes a mistake, the error message should say what went wrong and how to fix it, not just turn a box red.

8. Videos have captions

Recorded board meetings and promotional videos posted on your site need accurate captions. Auto-generated captions are a starting point, but proofread names and street names.

9. Pages work when zoomed to 200% and on a phone

Text should resize without breaking the layout, and the site should work on a small screen without sideways scrolling. A mobile-friendly site goes a long way toward meeting this.

10. PDFs are accessible, or available as web pages

This is the biggest job for most small towns. Agendas, minutes, ordinances, budgets and newsletters are often scanned images with no readable text. Our guide to accessible meeting agendas and minutes walks through fixing them.

What you probably don’t have to fix

The rule includes limited exceptions. Each comes with conditions, so read the DOJ’s guidance before you rely on one:

  • Archived content created before your compliance date, kept only for reference, stored in a clearly marked archive area, and not changed since it was archived.
  • Older documents such as PDFs posted before your compliance date, unless people still use them to apply for or access a current service.
  • Third-party content posted by others that you don’t control, like comments from residents.
  • Individualized, password-protected documents such as a single resident’s utility bill.
  • Social media posts published before your compliance date.

Even when content qualifies, you still have to provide it in an accessible format if a resident asks.

A realistic plan for a town with one clerk

Here’s how to work through the WCAG 2.1 AA checklist over the next year and a half:

  1. Now through spring 2027: Run an automated scan, then fix the site-wide problems in your theme first: contrast, focus outlines, heading order, menus. One fix in the theme repairs every page.
  2. Summer 2027: Move your most-used PDFs (agendas, minutes, fee schedules, forms) to accessible web pages or remediated PDFs. Set up an archive section for old documents.
  3. Fall 2027: Fix forms, add captions to videos, and train staff to post accessible content going forward.
  4. Early 2028: Do a manual keyboard and screen reader test, publish an accessibility statement with a contact for help, and keep a record of the work you’ve done.

The last step matters. If a complaint ever comes in, a written record showing steady good-faith progress is far better than a scramble.

Frequently asked questions

Does a village of 800 people really have to comply?

Yes. The rule covers every local government regardless of size. Smaller places simply get more time.

Is an accessibility overlay or toolbar enough?

No. A toolbar that lets visitors enlarge text or change contrast is a helpful extra, but it doesn’t fix missing alt text, broken keyboard navigation or scanned PDFs. The underlying site has to pass a full WCAG 2.1 AA checklist.

How much does ADA website compliance cost a small town?

It depends on how much content you have and how old your site is. For many small towns, moving to a modern, accessible website platform costs less than fixing an outdated site page by page. See how SnapSite handles ADA compliance.

Who should run this WCAG 2.1 AA checklist?

Anyone who posts to your site can handle the basics like alt text, link wording and headings. A web vendor should handle theme fixes, forms and a full audit.

Can we still use our current website?

Often, yes, if the theme can be repaired. If your site is built on an old platform that your vendor no longer updates, replacing it is usually faster and cheaper.

Get your town’s website ready for 2028

SnapSite builds and hosts ADA-focused websites for villages, towns, counties and special districts, with accessible meeting document tools built in. We’ll run this WCAG 2.1 AA checklist on your current site and show you what to fix first. We have worked with local governments since 2007. Explore our municipal websites or call (618) 539-2281 for a free accessibility review.

This article is general information, not legal advice. Check the DOJ’s Small Entity Compliance Guide and talk with your municipal attorney about your situation.

Share this article

Keep reading

Is your website ready for the ADA deadline?

Scan your site free, or talk with our team about an accessibility review.

Secret Link