The page count is not the audit scope
A sitemap, CMS export, and live link graph rarely agree. Without a preserved inventory and template map, you cannot explain what was included, what was sampled, or why the estimate changed.
For accessibility agencies
Accessibility audits that stay useful after launch
Pair change detection with WCAG scans. Attest the approved baseline, re-test what changed, and give clients a precise remediation scope.
The problems this solves
Every client deploy threatens your last audit
You sign off on WCAG conformance Friday. Client ships a theme tweak Monday. Your attestation is now a liability. You don't know about it until the client's user files a complaint.
Re-audits aren't billable if you can't scope them
"Please re-audit everything" is hard to quote. "These 3 pages regressed since our baseline, here's the delta" is a clean statement of work.
The six-step workflow
A repeatable engagement model from discovery through client remediation.
- 01
Generate the complete public-site scope
Start with the client's domain. OnChange proves the discovery boundary and preserves every canonical URL with capture outcomes instead of treating a partial list as the whole site.
- 02
Choose representative templates and journeys
Use the complete inventory, deterministic template families, critical flows, technologies, and risk to define the smaller set that needs expert manual testing.
- 03
After remediation, attest the baseline
When the client has signed off on the remediated state, mark that scan as the attested baseline. That's your VPAT snapshot.
- 04
Let change detection drive the rescans
When OnChange detects a text or visual change on a watched page, trigger a re-scan. The diff against the attested baseline shows exactly what regressed.
- 05
Send the delta report to the client
Every scan has a branded, print-ready report at /audit/:id. Share the URL. The client sees the new violations, WCAG criteria, and an AI-generated summary.
- 06
Invoice for the remediation work
Attested baseline plus rescan delta is a scope document. "Fix these 4 new AA failures" is a clean statement of work the client's engineering team can execute against.
What changes for your agency
- The complete inventory and the representative audit sample are both explicit
- Retainer clients get continuous conformance instead of annual audits
- Scope discussions shift from "what broke?" to "here's what broke, and here's what it costs"
- VPAT attestations stay meaningful between formal audit cycles
- Your team re-tests only the pages that actually need it
- Engineering handoff is a permalink, not an email chain
- Change history in OnChange doubles as your audit paper trail
Make accessibility a retainer, not a project
Continuous evidence makes the next remediation scope clear before another full audit begins.