For agencies
Ship the site. Keep the conformance. Bill the retainer.
OnChange gives digital agencies continuous WCAG monitoring, attested baselines for VPAT workflows, deploy-aware change attribution, and branded per-scan reports you can hand clients the same day.
The problem
Why this keeps showing up in your week.
Audit Monday, drift Tuesday
You ship a compliant site and sign off. Two weeks later a marketing tweak strips aria-labels, an image swap drops contrast, a rebrand renames the primary CTA. Your conformance claim is already stale, and you only find out when the client calls.
Client visibility is manual
Clients want "proof the site still works." Building that into a monthly status report means screenshots, manual re-audits, and spreadsheet tracking - billable hours that don't scale as your portfolio grows.
Regressions get caught by the client
A deploy breaks the contact form or the nav. Without continuous monitoring, the first report is a support ticket from the client, and now you're firefighting on their schedule.
Why OnChange
The specific parts that make this work.
Attested WCAG baselines
Mark any accessibility scan as the compliance baseline for a client. Every subsequent scan diffs against it and flags regressions - new violations, resolved ones, WCAG criteria affected, and specific selectors. VPAT attestations stay current between formal audits.
Attribution for every alert
When a monitored page changes, OnChange correlates the change with recent commits and returns a verdict like "Likely commit abc1234 caused the change, as renaming the hero link directly matches." You know which deploy broke what before the client notices.
Unlimited teams & clients
No per-seat billing and no per-client surcharges. Spin up one OnChange team per agency and invite as many teammates as you need; segment monitors with tags for each client.
Branded /audit/:id reports
Every accessibility scan has a print-ready report URL you can share with clients. Show baseline, current state, new violations, and the fix suggestions without building a PDF pipeline.
Per-monitor alert routing
Send each client's change alerts to their own Slack / Discord / email / webhook. Keep internal ops notifications separate from client-facing dashboards without running multiple accounts.
One feature set, every plan
Free through Enterprise all ship the same features. You only pay for volume: monitor count and check frequency. No gatekeeping on "premium" features like visual diffs, API monitoring, or accessibility scans.
The continuous-conformance play
Instead of selling an annual audit and hoping conformance holds, attach a retainer: OnChange monitors every client page, runs on-demand WCAG scans after every deploy, and surfaces regressions in a branded report you can hand the client the same afternoon. Higher ARPU, less firefighting.
See the a11y feature pageDeploy-aware client reporting
Pair OnChange's change detection with Git attribution to show clients exactly which deploy caused which regression. When the client asks "what changed?" - you have a commit link and a plain-English summary, not a post-mortem to write.
Learn about attributionMove your clients from annual audits to continuous conformance.
Start free, wire up your first client's monitors in an afternoon, and turn accessibility into a retainer line item by end of quarter.