How a Mid-Size City Went from ADA Complaint to Full WCAG Compliance in 60 Days
A formal DOJ complaint. 847 inaccessible PDFs. Keyboard navigation that trapped screen reader users in dropdown loops. The clock was already ticking, and the city needed a platform that could get to WCAG 2.1 AA without a two-year roadmap.
60
Days to full WCAG 2.1 AA conformance
847
PDFs identified and assessed for risk
11
Days from contract to platform launch
0
Open accessibility complaints post-launch
The Challenge: A Formal DOJ Complaint and 847 Inaccessible PDFs
January 2026. The city attorney opened an envelope from the Department of Justice and found a formal ADA Title II complaint against one of many mid-size local government agencies that had never audited their public-facing content. The resident who filed it uses a screen reader, and their letter named three specific barriers: PDFs published as image-only scans with no text layer, dropdown menus that trapped keyboard users in navigation loops, and permit and license forms whose fields carried no programmatic labels.
The IT director ordered an internal audit that afternoon. The numbers weren't pretty. An automated WCAG scan of the main city website flagged 1,243 distinct violations, and manual review confirmed 67% of them as Level AA failures with real user impact. Crawling the CMS for documents surfaced 847 PDFs going back nine years. Here's how that archive broke down:
- 312 PDFs were scanned images with no text layer at all, so a screen reader hits them and reads nothing
- 284 PDFs came out of Word or InDesign with tags, but with wrong reading order, missing alt text on charts, and no document title
- 251 PDFs had been partially remediated during a 2022 project and still failed at least one Level AA criterion
- 0 PDFs had been verified against the current WCAG 2.1 AA standard
The legacy CMS, deployed in 2017, had no accessibility checking of any kind. Every page, form, and PDF went live without a quality gate. Staff sat through a single half-day accessibility training in 2021, and structurally nothing changed after that. The city was publishing fresh violations every week and didn't know it.
PDF archive breakdown at audit
847 total
Nine years of documents crawled from the legacy CMS, sorted by failure pattern.
Why the City Chose WPPersona
Procurement had ten days. That's it. The city attorney had told the IT director that a credible remediation plan filed with DOJ inside 30 days would sharply reduce the odds of a formal consent decree. Speed mattered. So did substance.
Two of the three shortlisted platforms offered WCAG-compliant templates but couldn't show any platform-level enforcement on documents. Their pitch on PDFs was advisory. Train your staff, follow the guide, and hope for the best. Given that the city had just discovered 847 problem documents uploaded by well-meaning staff over almost a decade, the compliance officer wasn't going to accept another decade of the same pattern.
WPPersona's PDF scanner runs at upload, not after the fact. That's the piece the IT director cared about. During the demo, she uploaded three test PDFs: a scanned image, a badly tagged report, and a compliant document. The first two got blocked with specific failure codes (missing /MarkInfo, no /Title entry, no logical reading order) and remediation steps. The third passed instantly. No handwaving.
“Every platform we looked at told us to train our staff better. WPPersona was the only one that built the quality gate into the upload workflow itself. That's the structural change we needed to prevent this from happening again.”
IT Director, City Government
The Solution: 11-Day Onboarding, 60-Day Compliance
Days 1 to 11: Platform Launch
The implementation team moved the city's 214 core pages across 8 department sections onto the new WCAG-compliant platform. Brand colors got applied to the default theme, then every contrast ratio was checked against the 4.5:1 minimum for normal text and 3:1 for large text. Keyboard navigation was tested in every menu state. The skip-to-content link went in and was verified with JAWS 2025 and NVDA. Focus indicators hit 3:1 contrast against adjacent colors. On Day 9, DOJ counsel got access to a staging URL, which mattered as evidence that remediation was already underway.
Days 12 to 35: PDF Triage and Remediation
WPPersona's PDF audit tool ran across the full archive. All 847 documents were scored against a risk matrix that weighed document type (public-facing vs. archival), traffic volume, and severity of the WCAG failure. The 312 image-only PDFs got flagged Critical and went out to a contracted remediation vendor for OCR and PDF/UA tagging. The 284 tagged-but-broken documents went to two city staff who had trained on Adobe Acrobat Pro's tagging panel and Reading Order tool. Of the 251 previously-remediated documents, 189 cleared the re-scan. The remaining 62 got targeted fixes.
Days 36 to 60: Validation and Conformance
By Day 36, every high-traffic, high-risk PDF had been either remediated or swapped for an accessible HTML page. The IT team hired a third-party auditor to run a manual pass across 40 representative pages, 3 online forms, the interactive permit portal, and a random sample of 50 PDFs from the remediated archive. The audit came back with 4 minor Level A findings, all fixed inside 48 hours. On Day 60, the city posted its Accessibility Statement at its main domain, sent DOJ a compliance documentation package, and issued a press release announcing WCAG 2.1 AA conformance.
WCAG 2.1 AA violations across the 60-day plan
1,243 to 0
Outcomes
WCAG 2.1 AA violations (main site)
Before
1,243
After
0 confirmed
PDFs at Critical risk level
Before
312
After
0 (remediated or replaced)
PDFs at High risk level
Before
284
After
0 (remediated)
Days to platform launch
Before
120+ (competitor estimate)
After
11
DOJ closed the complaint inquiry without a formal consent decree. The city attorney credited three things: the fast platform migration, a documented PDF remediation workflow, and a live Accessibility Statement at launch. That combination did more for the city than any legal argument.
The city's publishing model looks different now. Every PDF uploaded through WPPersona gets scanned at the moment of upload. If a staff member tries to publish a document with missing tags or no title, they see an inline error with the exact fix. The old pattern, where anyone could publish anything and hope for the best, is gone. The quality gate is in the platform, and it requires no ongoing training to keep working.
Facing a Similar Situation?
Whether a complaint just landed on your desk or you're trying to get ahead of the April 2027 deadline, WPPersona's built-in PDF scanning and WCAG-compliant platform can move your team fast.
Schedule a Free Demo