How a Small Township Achieved 100% WCAG Compliance for $99/Month
4,800 residents. No IT staff. A legacy CMS costing $8,400/year with no accessibility features. Here's how the township got compliant, got modern, and saved $7,212 per year.
$99/mo
WPPersona Starter plan cost
86%
Reduction in annual web costs
100%
WCAG 2.1 AA conformance achieved
0
Technical staff required post-setup
The Small Government Accessibility Problem
Small municipalities carry the same ADA Title II obligations as their bigger neighbors. Townships, villages, and boroughs under 10,000 people. Same rulebook, almost none of the budget. This small township government (population 4,800) looks like hundreds of other small local government agencies: one clerk, one part-time DPW admin, and a website that got built once and then quietly aged.
The Township Clerk was the de facto webmaster. She didn't ask for the job. It just landed on her desk in 2016 when a local design firm handed over the finished site and moved on. Annual cost sat at $8,400. That covered hosting, a proprietary CMS license, and a support contract that allowed exactly 20 content changes per year. Change number 21 cost $125/hour and required a support ticket.
The accessibility picture was bad. An AXESS audit commissioned by the township attorney in early 2026, triggered by a resident asking about the April 2027 deadline, came back with the kind of findings you don't want to hand your council on a Monday night:
- The site failed 58 of 78 applicable WCAG 2.1 AA success criteria
- All 34 PDFs on the site (meeting minutes, zoning notices, tax forms) were published without any accessibility verification
- 19 of the 34 PDFs were scanned images with no text layer. Completely inaccessible to screen readers.
- The contact form had no labels. Screen reader users heard only unlabeled input fields.
- The navigation menu was mouse-dependent. Keyboard users could not open any dropdown.
- The site had no accessibility statement and no feedback path for residents with disabilities
The township's web vendor quoted $18,500 to fix the existing site and bring it to WCAG 2.1 AA. That quote assumed staff could be trained to maintain accessibility going forward, which the Clerk pushed back on hard. “I know how to write and post agendas,” she told the township council. “I don't know how to check PDF tagging structures.”
WCAG 2.1 AA criteria: audit findings
58 of 78 failed
AXESS audit result for a small township, early 2026. Applicable WCAG 2.1 AA success criteria only.
Annual web spend by option
$7,212 saved / year
Recurring yearly cost for a 4,800-resident township. Upfront rebuild fees excluded.
The Council Approval Process
The Clerk walked the Township Committee, the five-member elected body that governs the township, through a plain framing. The current vendor couldn't hold compliance even after an expensive remediation. And the per-change billing model was breaking an already thin operating budget.
She brought a three-option comparison to the meeting:
Option A: Remediate existing site
$18,500 upfront + $8,400/year ongoing
Doesn’t prevent future violations. The Clerk still can’t self-manage content without accessibility expertise.
Option B: Full custom rebuild
$35,000 to $60,000 upfront + $4,800 to $9,600/year
Accessible at launch, then depends on staff training to stay that way. No automated enforcement.
Option C: WPPersona Starter Plan
Recommended$99/month ($1,188/year)
Built-in PDF scanning, WCAG-compliant templates, no IT staff needed. The Clerk self-manages content.
The Committee voted 4-1 to approve Option C. The dissenting member wanted a second bid on the custom rebuild. After seeing the implementation timeline (14 days vs. 6+ months), she flipped and supported the WPPersona platform at the following meeting.
Time from approval to live site
14 days on Option C
Elapsed calendar days between Township Committee approval and public launch. 6+ months shown as 180 days.
Upfront cost to get to WCAG 2.1 AA
$0 upfront on Option C
What the Clerk Can Do Now, Without IT Help
The Clerk's workflow changed the week the platform went live. Here's what she owns end to end now, with no support ticket and no vendor call:
Post meeting minutes
Before
Upload PDF to old CMS, email vendor if changes needed. No accessibility verification.
After
Upload PDF to WPPersona. Automatic scan confirms compliance. Publish. Three minutes.
Publish zoning notices
Before
Vendor support ticket. Three-day turnaround. $125/hour once past 20 requests/year.
After
Self-service page with an accessible template. Same-day publish. No extra cost.
Update department contacts
Before
Vendor change request. Two or three business days.
After
Inline editing. Two minutes. Live immediately.
Respond to a resident accessibility complaint
Before
No feedback mechanism. No accessible alternative documents.
After
Accessibility statement with a contact link. If a document gets flagged, the WPPersona dashboard shows the specific issue and the fix steps.
“I manage the whole township website myself now. I post the agendas, update the calendar, and when I upload a document, I know right away whether it's going to be accessible. Before, I had no idea. I just hoped things were okay. Now I know.”
Township Clerk, Small Township
Small Town or Township?
WPPersona's Starter plan at $99/month was built for small governments with big compliance obligations and thin budgets. No IT staff needed.
Schedule a Free Demo