WCAG 2.1 AA Guide: 10 Simple Solutions for Rural Communities (2028)
If your village, town, or special district has a population of fewer than 50,000, this WCAG 2.1 AA checklist will serve as your guide to achieving compliance with the ADA regarding your website. The U.S. Department of Justice has extended the deadline for compliance to April 26, 2028. While this may seem like a distant date, if you have limited resources such as a part-time clerk, a backlog of scanned documents, and no dedicated IT staff, the time to act is now.
This guide specifically targets small towns, omitting complex legal jargon and instead providing a practical checklist of what to evaluate, how to prioritize fixes, and what can be deferred. For complete information on the recent deadline adjustment, refer to our article The ADA Website Deadline Moved — Your Risk Didn’t.
Who is Required to Comply and By When
The DOJ’s Title II regulation applies to all state and local government websites and mobile applications, encompassing 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 specified standard for compliance is WCAG 2.1 Level AA. Additionally, the DOJ has requested public feedback on potentially easing the compliance burden for smaller governments, which may lead to further revisions in the future. However, it’s essential to recognize that the fundamental ADA obligation to accommodate residents with disabilities is already in effect, and complaints will arise regardless of these deadlines.
The WCAG 2.1 AA Compliance Checklist for Small Municipalities
While the WCAG guidelines include numerous success criteria, this checklist focuses on ten critical items that our audits of small-town websites indicate are the most commonly encountered issues.
1. All Images Have Descriptive Alt Text
Images such as pictures of the water tower, new park structures, or local events must include concise descriptions that can be read by screen readers. Images used for purely decorative purposes, like background graphics, should be tagged accordingly to be disregarded by screen readers.
2. Sufficient Color Contrast for Text
Typical text should have a contrast ratio of at least 4.5:1 compared to its background. Common issues include light gray text on a white background or white text on light blue banners. Free contrast checkers can quickly verify compliance.
3. Keyboard Navigation is Essential
Try paying a water bill or submitting a form using just the Tab and Enter keys without a mouse. If keyboard navigation fails on menus, sliders, or pop-ups, these are automatic compliance issues.
4. Keyboard Focus is Clearly Indicated
When navigating through the page, there should be a visible outline indicating which link or button is currently selected. Many web themes omit this outline, but it is crucial for accessibility. Make sure it is reinstated.
5. Headings Follow a Logical Structure
Each webpage should contain a single main heading (H1) followed by subheadings (H2, H3). Users with screen readers navigate between headings similarly to how sighted visitors might skim the page, so ensure headings are ordered logically rather than based solely on font size preference.
6. Link Text is Descriptive
Generic phrases like “Click here” or “Read more” fail to convey context to screen reader users. Instead, use descriptive text, e.g., “Download the March 2027 board agenda (PDF)”.
7. Forms Need Labels and Clear Error Messages
Each individual field in your forms, including FOIA requests, service requests, and contact forms, must have a visible label linked in the code. Error messages should be informative, stating what went wrong and how to correct it, rather than simply highlighting the error.
8. Videos Require Captions
Any videos, such as recorded meetings or promotional content hosted on your site, must have accurate captions. Automatic captions can serve as a starting point, but ensure they are reviewed for accuracy, especially regarding names and locations.
9. Zoom Accessibility and Mobile Compatibility
The site should accommodate text resizing up to 200% without disrupting the layout and function properly on mobile devices without requiring horizontal scrolling. A responsive design significantly assists with this requirement.
10. PDFs Must Be Accessible or Available as Web Pages
This is often the most considerable challenge for small towns. Common documents like agendas, minutes, ordinances, and newsletters frequently exist as scanned images without readable text. Our guide on accessible meeting agendas and minutes provides strategies for improvement.
Content You May Not Need to Fix
There are specific exceptions within the rule. Each exception is subject to conditions, so consult the DOJ’s guidelines for clarity:
- Archived Content: Materials produced before your compliance date that are retained solely for reference, are stored in a clearly labeled archive, and have not been modified since being archived.
- Old Documents: PDFs published before your compliance date, unless they are still utilized for current services.
- Third-Party Content: User-generated content or comments that you do not have control over.
- Password-Protected Documents: Specifically individualized documents, such as a utility bill for a single resident.
- Social Media Content: Posts made prior to your compliance deadline.
Even if content qualifies for an exception, you are still required to provide it in an accessible format if requested by a resident.
A Practical Plan for a Town with Limited Resources
Here is a recommended timeline to navigate the WCAG 2.1 AA checklist over the next year and a half:
- Now through Spring 2027: Conduct an automated site audit, then address site-wide issues within your theme first—such as color contrast, keyboard focus outlines, heading hierarchy, and navigation menus. Fixing the theme can often address multiple pages at once.
- Summer 2027: Transition your most frequently used PDFs (including agendas, minutes, fee schedules, and forms) to accessible web pages or convert them to compliant PDFs. Create an archive section for older documents.
- Fall 2027: Update forms, add captions to videos, and provide staff training on creating accessible content going forward.
- Early 2028: Perform a manual testing session using a keyboard and screen reader, publish an accessibility statement with a contact for inquiries, and keep a detailed record of the improvements you’ve made.
The final step is particularly essential. In the event of a complaint, having documented evidence of consistent good-faith efforts to address accessibility issues is far preferable to rushing to fix everything at once.
Common Questions
Is compliance mandatory for a village with only 800 residents?
Yes. Every local government entity, regardless of size, is covered by this rule. Smaller towns simply have more time to comply.
Is using an accessibility overlay or toolbar sufficient?
No, while an overlay that allows users to adjust text size or contrast is beneficial, it does not address critical issues such as missing alt text, inadequate keyboard navigation, or inaccessible scanned PDFs. The underlying website must comply with the entire WCAG 2.1 AA checklist.
What is the cost of ADA website compliance for a small town?
The cost varies significantly depending on the amount of content and the age of the website. In many cases, migrating to a modern and accessible website platform may be less expensive than incrementally fixing an outdated site.
Explore how SnapSite handles ADA compliance.
Who should be responsible for this WCAG 2.1 AA checklist?
Anyone involved in posting content to your site can manage fundamental tasks like adding alt text, descriptive link text, and organizing headings. However, a web vendor should oversee more complex tasks involving theme fixes, form accessibility, and comprehensive audits.
Can we continue using our existing website?
In many cases, yes, as long as it’s possible to rectify the theme. However, if your site is built on an older platform that is no longer supported, replacing it may be the more efficient route.
Prepare Your Town’s Website for 2028
At SnapSite, we specialize in developing and hosting ADA-compliant websites for villages, towns, counties, and special districts, equipped with tools for accessible meeting documents. We can evaluate your current site against the WCAG 2.1 AA checklist and prioritize necessary fixes. With experience working alongside local governments since 2007, we are here to assist.
To learn more about our municipal website solutions, explore our offerings or call (618) 539-2281 for a complimentary accessibility review.
This article provides general information and is not intended as legal advice. For specific inquiries regarding your situation, please refer to the DOJ’s Small Entity Compliance Guide and consult with your municipal attorney.



