What a Title II compliance pass actually includes
1 — Inventory
Before anyone audits anything, the entity needs to know what it's responsible for: the main site and its subdomains and microsites, the pages, the forms, the embedded third-party services (payments, agendas, GIS, recreation signup), the mobile apps, and — the big one for government — the documents. Agendas, minutes, budgets, notices, applications: often thousands of PDFs, of which a meaningful share falls under the rule's exceptions. The inventory sorts covered from excepted, so remediation effort lands where the obligation actually is. This sorting alone changes the size of the project, usually downward.
2 — Audit
A WCAG 2.1 AA review of the templates and the highest-traffic flows, tested the way conformance will eventually be tested by someone else: with the underlying code and a screen reader, not an automated badge. Government sites are template-driven — one news template, one department template, one form pattern — so findings concentrate at the template level, and each finding is mapped to the success criterion it fails. Automated scanners contribute coverage; they don't substitute for the manual pass, because most of WCAG can't be machine-verified.
3 — Template and content remediation
Fixes in the actual CMS templates and theme code: heading structure, landmarks, form labels and error handling, keyboard operability, focus management, color contrast, accessible names on controls, link purpose. Because the fixes land in templates, they propagate — one corrected form pattern fixes every page that uses it, and every page created after it.
4 — Document remediation
The covered documents get a triage: regenerate from source where the source exists (the cheapest path — a correctly exported agenda is accessible at no extra cost forever after), remediate individually where it matters, and fix the publishing pipeline so tomorrow's documents come out conformant by default. An entity that only fixes yesterday's PDFs will be back where it started in a year.
5 — Validation and the conformance record
The remediated templates and flows are validated with assistive technology, and the engagement closes with a dated conformance report: what was reviewed, what was changed, how each criterion stands, what's excepted and why. That's the record your office holds on the compliance date — and the posture you want if anyone ever asks to see your work.
Built for how government buys
Fixed scope, fixed number, deliverables defined in writing before anything starts — the shape procurement can approve without a committee inventing it. One engineer, direct communication with your IT staff or vendor, and every deliverable usable by whoever maintains the site after me.
Contact
Email [email protected]. You'll get a reply from me — usually the same day, always from a person.