The Small Government Reality
Picture Millbrook Township, Michigan. Population 3,200. The entire municipal technology footprint consists of two aging desktops, a shared printer that jams every Thursday, and a WordPress website the previous clerk's nephew built in 2018. The person responsible for that website is also the deputy treasurer, the notary public on staff, and the one who unlocks the town hall every morning. There is no IT department. There is no accessibility budget. There is, in fact, no line item in the entire general fund with the word “digital” in it.
This is not an edge case. It is the overwhelming norm of American local government.
of U.S. municipalities have fewer than 10,000 residents — and nearly all of them operate websites with no dedicated accessibility staff.
According to U.S. Census Bureau data, of the roughly 19,500 incorporated municipalities in the United States, more than 16,500 have populations under 10,000. Most have under 2,500. The majority of those communities have websites that have never received a formal accessibility audit. They post meeting minutes as scanned PDFs. Their contact forms were built with a plugin that hasn't been updated since the Obama administration. And their staff — genuinely dedicated public servants — have no idea any of this is a legal liability.
Towns like Sublette, Kansas (population 1,400). Or Orland, Maine (population 2,100). Or Caliente, Nevada (population 1,100). These are real places with real residents who use wheelchairs, experience vision impairments, or rely on screen readers to navigate the web. They are constituents just like everyone else, and federal law says they are entitled to equal access to government information and services — including the town website.
This guide was written for the person who manages that website on top of everything else. We're going to be honest about what the law requires, practical about what it actually takes, and specific about how small towns can get there without hiring a consultant or redesigning from scratch.
Why the Deadline Still Applies to You
On April 24, 2024, the Department of Justice published a final rule under Title II of the Americans with Disabilities Act establishing specific technical standards for state and local government websites. The rule adopts Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as the compliance standard. It is not a suggestion. It is binding federal regulation.
The compliance deadlines are tiered by population:
April 24, 2026
Title II entities with 50,000+ population
Large cities, counties, and state agencies must comply.
April 26, 2028 — Your Deadline
Title II entities under 50,000 population
Small towns, townships, villages, and special districts must comply. This is not optional.
Two years sounds like a long runway. It is not. Website remediation, content auditing, staff training, and platform migration — if needed — all take time, and procurement in small government moves slowly. The towns that will struggle most in 2028 are the ones that assume 2027 is early enough to start.
DOJ complaints do not filter by population size.
A resident of a town of 800 people has exactly the same right to file an ADA Title II complaint with the Department of Justice as a resident of Chicago. The enforcement mechanism does not exempt small governments. Complaints trigger investigations, investigations produce findings, and findings can result in corrective action agreements, consent decrees, and civil litigation. The fact that your town has never been audited is not protection — it is luck.
There is a persistent and dangerous myth in small local government that size confers invisibility. “We're too small for anyone to care.” We have seen this belief shattered by disability rights organizations that specifically target smaller governments precisely because the violations are easy to document and the settlements are often quick because small towns can't afford litigation. Size does not protect you. It may make you a softer target.
The 5 Most Common Violations in Small Town Websites
After reviewing hundreds of small municipality websites, the same violations appear again and again. These are not obscure edge cases — they are the structural patterns of how small towns built their web presence before accessibility was on anyone's radar.
Scanned PDF Meeting Minutes Without OCR
This is the single most common violation we encounter. A staff member prints the minutes, signs them, scans them to PDF, and uploads the resulting image file. To a screen reader, that file is a blank page. A resident who is blind has no way to read what happened at the council meeting.
Why it happens: The workflow feels natural — sign a paper document, scan it, done. The fix requires either running OCR on the scanned file, creating the minutes as a native text document from the start, or using a PDF remediation tool.
Missing Alt Text on Staff Photos and Department Headers
Staff directory pages almost universally have untagged images. The department header graphic — a photo of town hall with the words “Public Works Department” baked into the image — is read as nothing by assistive technology. The mayor's headshot has an alt attribute that reads “IMG_20230415_094832.jpg.”
Why it happens: Image alt text is invisible to the person uploading content. Without training and a CMS that enforces it, content authors simply never think about it. This is a training and tooling problem simultaneously.
Online Forms That Are Not Keyboard Navigable
Permit applications, variance request forms, contact forms, event registration — these are the most important transactional parts of a municipal website. They are also frequently built with plugins that use custom UI elements without proper ARIA roles, broken tab order, or focus traps that trap keyboard users inside a dropdown they can never exit.
Why it matters most: A resident with motor disabilities who cannot use a mouse cannot submit a building permit application. This is precisely the kind of barrier Title II was designed to eliminate. Keyboard accessibility is non-negotiable under WCAG 2.1 AA.
Embedded Google Maps Without an Accessible Alternative
Nearly every small town website has an embedded Google Map on the contact or directions page. The embed itself is not fully accessible — it provides inconsistent screen reader experience and no keyboard-navigable way to get meaningful location information. WCAG requires a text alternative that provides equivalent information.
The fix is simple: Add a text address, written directions, and a link to the accessible Google Maps URL alongside the embed. Fifteen minutes of work that eliminates the violation entirely.
Meeting Agenda PDFs That Are Photos of Paper Documents
Distinct from scanned minutes, agenda PDFs are sometimes literally a photograph of a typed or handwritten page, posted before a meeting. No text layer. No tags. No document structure. From an accessibility standpoint, this is identical to attaching a JPEG and calling it a document.
Root cause: Agendas are often prepared by board members at home and emailed to staff as images. The fix requires shifting to a simple Word or Google Docs template that is exported as a tagged PDF — a one-time process change that costs nothing but takes intentional implementation.
A Budget-Realistic Compliance Roadmap
This roadmap is designed for towns with minimal budget, 1–2 staff who can dedicate a few hours per month, and no existing accessibility program. It prioritizes impact on residents first and cost second.
Run the WAVE browser extension on every page of your website. Export the results. Run Accessibility Insights for Web on your five most-visited pages (use Google Analytics, or guess: home, contact, meeting minutes, permits, departments). Document every error and alert.
Address every image missing alt text, add text addresses next to all embedded maps, check and correct color contrast on primary buttons and headers using the WebAIM Contrast Checker (free), and update page titles to be descriptive. These changes are low-skill, high-impact, and take an afternoon in most CMS editors.
Inventory all PDFs on the site. Categorize: (a) documents that can be replaced with an accessible HTML page, (b) documents that need OCR and tagging, (c) documents that need to be recreated from source. Use Adobe Acrobat's free accessibility checker (built into Acrobat Reader) to identify which PDFs have no text layer. For high-volume remediation, Adobe Acrobat Pro at $19.99/mo is often sufficient for small-town document libraries.
Manually test every form with only a keyboard. Tab through every field. Confirm you can submit successfully without a mouse. If you cannot, the form is non-compliant. For WordPress sites, replacing inaccessible form plugins with Gravity Forms (which has strong accessibility support) or WPForms Lite often resolves structural issues. For custom forms, you may need a developer for 2–4 hours.
The DOJ rule requires covered entities to post an accessibility statement with a feedback mechanism. Use the W3C's free Accessibility Statement Generator at w3.org/WAI/planning/statements/generator. Post it in your footer. This demonstrates good faith compliance effort, is legally required, and takes less time than a staff meeting.
Quick Wins You Can Do This Week
You don't need a project plan to start. These actions take under an hour each and move you measurably closer to compliance today.
Install the WAVE Browser Extension
Available free for Chrome and Firefox at wave.webaim.org. Run it on your homepage right now. The red icons are errors. The yellow icons are alerts. Spend 20 minutes understanding what is flagged — no technical background required, every issue has a plain-English explanation.
wave.webaim.org — freeCheck Your PDFs With Adobe Acrobat Reader
Open any meeting minutes PDF. Go to View → Read Out Loud → Activate Read Out Loud. Then press Shift+Ctrl+V to read the current page. If nothing is read, or if the text makes no sense, the PDF has no accessible text layer and needs remediation.
Adobe Acrobat Reader — freeTest Your Contact Form With Only a Keyboard
Put your mouse in a drawer. Use only Tab, Shift+Tab, Enter, and Space to fill out and submit your contact form. Can you do it? If your focus disappears into a void, if you can't activate the submit button, or if a dropdown traps you — you have a keyboard accessibility failure.
No tools requiredRun Accessibility Insights Fast Pass
Download Accessibility Insights for Web (free, from Microsoft) and run the FastPass test on your five most-visited pages. It checks for the ~40 issues most commonly flagged in DOJ enforcement, takes under two minutes per page, and produces an export you can keep as documentation of good-faith effort.
accessibilityinsights.io — freeAdd Alt Text to Your Last 10 Uploaded Images
In WordPress, go to Media Library. Look at your most recently uploaded images. Click each one. If the Alt Text field is blank, fill it in with a description of what the image shows. "Mayor Jane Smith at the ribbon cutting for Riverside Park, June 2025." This takes five minutes and immediately closes a violation.
In your CMS — freePro tip: Document everything.
Every audit you run, every fix you make, every training session you attend — log it with a date. This documentation is your best defense if a complaint is ever filed. The DOJ gives significant weight to documented good-faith compliance efforts when determining remedies.
Making the Case to the Council or Board
The hardest part of small-town compliance is often not the technical work — it's persuading elected officials to allocate resources to something they can't see and that hasn't hurt anyone yet. Here is how to make that case effectively.
Frame it as risk management, not technology spending.
Council members who would vote against “website accessibility upgrades” will often vote for “reducing the town's exposure to federal civil rights litigation.” The framing matters. You are not asking for money for IT. You are asking for an insurance premium.
Average ADA website lawsuit settlement range for government entities
Typical legal defense cost before a case is resolved, regardless of outcome
Approximate annual cost of a fully compliant CMS platform for small towns
Use the federal mandate, not your opinion.
Bring the actual DOJ final rule to your presentation. Print the relevant pages. Point to the April 26, 2028 compliance date in the Federal Register. When elected officials see that this is a federal mandate — not a staff suggestion — the conversation changes. You are not advocating for accessibility. You are informing the board of a legal obligation.
Cite a nearby comparable entity.
Nothing focuses a small-town board like hearing what happened to the neighboring county or a town two hours away. Research whether any municipalities in your state have received DOJ complaints or entered corrective action agreements regarding web accessibility. This information is public record and searchable at ada.gov/cases.
Script for your next council meeting:
“The Department of Justice has issued a final rule under the Americans with Disabilities Act requiring all municipalities under 50,000 residents to bring their websites into compliance with WCAG 2.1 AA by April 26, 2028. Non-compliance exposes the town to federal complaints, investigations, and potential litigation with settlements averaging $25,000 to $75,000 plus legal costs. We have identified the specific issues on our current site and have a plan to address them. I'm requesting [X] to begin remediation this fiscal year.”
Procurement Shortcuts for Small Towns
Small governments often don't have procurement staff. The idea of issuing an RFP for web accessibility services is genuinely daunting when the same person who would write the RFP also answers the phones. Here is how to shortcut the process legally.
NASPO ValuePoint Cooperative Contracts
The National Association of State Procurement Officials (NASPO) runs ValuePoint, a multi-state cooperative purchasing program. Many state-level IT and web services contracts are accessible through NASPO, meaning your town can piggyback on a competitively bid contract without running your own RFP. Check nasponetwork.org for contracts in your category.
State Purchasing Schedules
Most states maintain master price agreements for technology goods and services that any unit of local government can use without a separate competitive process. Check your state procurement office's website for “cooperative purchasing,” “master contract,” or “statewide contract” for web services or accessibility technology.
Municipal League Programs
State municipal leagues and associations of townships often negotiate group technology contracts for their members. Leagues in Michigan, Pennsylvania, Ohio, and Illinois, among others, have historically offered CMS and website programs to member municipalities. Contact your state league directly — they exist specifically to solve these problems for small governments.
Piggyback Contracts
If a neighboring county or school district already has a competitively bid web accessibility contract, ask if you can piggyback. Many contracts include language permitting other public entities to use the same pricing. This is legal in most states and requires nothing more than a letter agreement between entities.
Procurement tip for towns under 5,000:
Many states have small-purchase thresholds — often $10,000 to $25,000 — below which you can issue a purchase order without a formal competitive bid. A CMS subscription that falls below your threshold can be procured by quote rather than RFP, dramatically simplifying the process. Know your threshold before you assume you need a multi-month procurement cycle.
The Small Town Success Pattern
What does actual, sustained compliance look like for a 2-person team in a town of 3,000 people? Not a theoretical best practice — a real, livable cadence that doesn't require your staff to become accessibility experts.
Monthly (30 min)
- Check alt text on all images added that month
- Verify new PDFs have text layers before posting
- Review any accessibility feedback received
Quarterly (2 hours)
- Run WAVE scan on full site, document results
- Keyboard-test any new forms or interactive features
- Update accessibility statement with any changes
Annual (half day)
- Formal accessibility audit (automated + manual)
- Staff training refresher (1 hour, online free via W3C)
- Report to council on compliance status
This cadence represents approximately 10–12 hours of dedicated compliance work per year beyond initial remediation. That is not a burden. It is a professional responsibility that protects residents, protects the municipality, and is well within the capacity of any clerk or administrator already managing a municipal website.
What WPPersona Gives Small Towns
Everything described in this guide is achievable on an existing website with enough time, skill, and determination. But many small towns will reach a point where patching an old WordPress installation is more expensive — in staff time and ongoing risk — than starting fresh on a platform built for compliance from the ground up. That's where WPPersona comes in.
WCAG 2.1 AA Built In
Every theme, template, and component in WPPersona is built to WCAG 2.1 Level AA. Color contrast, keyboard navigation, ARIA roles, focus management — it is part of the platform, not an add-on. You do not remediate. You do not audit for baseline compliance. It is done.
Accessible Document Workflows
Meeting minutes, agendas, and public notices uploaded through WPPersona are processed through our document accessibility pipeline. Scanned PDFs are automatically flagged. Native exports from Google Docs and Word are optimized for text accessibility on upload.
Compliance Dashboard
A real-time dashboard shows your accessibility status, flags new content that may introduce issues, and generates the documentation you need for your annual report to the council or for a DOJ response if a complaint is ever filed.
Forms That Just Work
Every form in WPPersona — permit applications, variance requests, contact forms, event registrations — is built on a fully keyboard-accessible, ARIA-compliant form engine. Residents who rely on assistive technology can use every feature without workarounds.
DIY Compliance vs. WPPersona
| Factor | DIY on Existing Site | WPPersona |
|---|---|---|
| Initial compliance effort | High — audit, remediate, test | None — compliant at launch |
| Ongoing maintenance | 10–20+ hrs/yr of manual checking | Automated monitoring included |
| Document accessibility | Manual remediation per document | Automated pipeline on upload |
| Form accessibility | Plugin-by-plugin audit required | Fully accessible out of the box |
| Staff training required | Significant — ongoing | Minimal — platform enforces standards |
| Cost | $0–$500+ in tools, significant staff time | Starts at $99/mo — all-in |
| Risk if complaint filed | Depends on remediation completeness | Platform compliance documented |
| Time to compliance | Months of active work | Day one of launch |
The math is straightforward.
One hour of accessibility consulting runs $150–$300. One DOJ complaint investigation can consume hundreds of staff hours. WPPersona at $99/month is $1,188/year — less than the cost of eight hours of compliance consulting, less than the first deductible on any meaningful legal action, and a budget line item your council can approve in a single meeting.
You Don't Have to Solve This Alone
The towns that will reach April 26, 2028 in compliance are not the ones with the biggest IT budgets. They are the ones that started early, documented their progress, used the free tools available to them, and made smart platform choices that did the compliance work for them.
You serve a community. Your website is part of that service. When a resident with a visual impairment tries to find the meeting minutes, download a permit application, or contact their township trustee — they deserve the same access as every other resident. That principle is not bureaucratic overhead. It is the point of public service.
The deadline is real. The tools are available. The path is clear. Start this week.
Ready to check your site today?
WPPersona gives small towns and townships a fully WCAG 2.1 AA compliant website platform starting at $99/month — built for the public sector, designed for lean teams, and ready to meet the April 2028 deadline from day one.