A Water Special District: ADA Compliance With No IT Staff

The Challenge: A 14-Year-Old Website, No IT Staff, and a Compliance Deadline

Special districts in the SLED sectorsit in an awkward spot under ADA Title II. Cities and counties have IT departments, comms teams, and legal counsel on speed dial. Most special districts don't. They run on skeleton crews who wear five hats before lunch. At a regional water special district, a public agency serving 190,000 residents, the website was one of those hats. Two admins handled it alongside public records requests, board meeting coordination, and customer service phone calls.

The site was built in 2012. The CMS behind it was discontinued by the vendor in 2019. It still ran, technically. No security patches. No accessibility fixes. No support line to call when something broke. The administrative coordinator had asked for a replacement three times in five years. Every request got deferred to next budget cycle.

Then DOJ published the Title II final rule in 2024. The general manager took the deadline to the board. A consultant walked the current site against WCAG 2.1 AA. The findings were rough:

• The site failed 71% of automated WCAG 2.1 AA success criteria. The highest failure rate the consultant had seen across 40 agency assessments.
• All 134 PDFs on the site went up without a single accessibility check. Water quality reports, board agendas, and rate schedules were the most-downloaded of the bunch.
• The contact form had no keyboard accessibility. Form fields lacked programmatic labels.
• No skip-to-content link. No ARIA landmarks. Heading levels used for visual styling, not semantic structure.
• The CMS itself could not produce accessible output. Fixing the template meant rebuilding the platform.

The consultant's call was blunt. Replace the platform, don't patch it. For a special district with no IT staff, that usually means hiring a consulting firm for a 6-to-9-month engagement at $60,000 to $120,000. The district didn't have the budget. And the timeline didn't line up with the compliance deadline anyway.

Finding a Solution Built for Non-Technical Staff

The administrative coordinator would be the primary user of whatever came next. She set one rule for the vendor evaluation. She had to be able to publish a water quality report, a board agenda, or a rate schedule without calling anyone for help. If the platform needed HTML, ARIA attributes, or CSS, it was wrong for a two-person office. End of story.

The WPPersona demo skipped the marketing tour. It went straight to the document workflow. The coordinator dropped a live water quality report into the interface. 24 pages. Tables of chemical readings, regulatory thresholds, health advisory notes. The scan came back in seconds: passed all five accessibility criteria. Two clicks later, it was live.

Then she uploaded a three-year-old board agenda. A scanned image, no text layer. The platform flagged two failures on contact: no text layer, no document title metadata. Inline guidance told her what to do. Run OCR through the built-in tool, upload an HTML version instead, or send it to the WPPersona accessibility support team. Nothing on the list required IT.

The 7-Day Launch

WPPersona's rollout at the water district ran on a timeline built for agencies with no in-house technical bench:

Staff Capability: Before and After

Compliance Timeline and Ongoing Operations

Six weeks after launch, the general manager brought the compliance package to the board's next regular meeting. Inside the package: a WCAG 2.1 AA conformance report from a third-party audit, the PDF risk remediation summary, and the published Accessibility Statement on the new site. The board adopted a formal Digital Accessibility Policy referencing WCAG 2.1 AA. They named the administrative coordinator as the agency's ADA web coordinator.

Eighteen months in, the district publishes an average of 14 documents a month. Water quality reports, board packets, public notices, rate schedules. Every one gets scanned at upload. Failures are caught before publish and routed to the coordinator with specific remediation steps. Since go-live, not one non-compliant document has made it onto the site. Monthly cost: $199 on the WPPersona Special District plan. That's a fraction of the $60,000-plus a traditional website replacement would've run.