Accessibility monitoring is the ongoing process of scanning and reviewing a digital asset to detect new WCAG conformance issues as they appear. It sits between audits, filling the gap where content changes, code updates, and new features can introduce accessibility issues that did not exist when the last evaluation was completed.
Monitoring does not replace a (manual) accessibility audit. It extends the value of one. After an audit identifies issues and remediation addresses them, monitoring watches for regressions and new problems so the asset does not quietly fall out of conformance.
| Aspect | Detail |
|---|---|
| What it does | Tracks a website, web app, or mobile app for new accessibility issues on a recurring basis |
| What it does not do | Replace a (manual) audit or determine full WCAG conformance |
| When to start | After an initial audit and remediation cycle is complete |
| Typical frequency | Weekly, biweekly, or monthly scans depending on how often content changes |
| Standard | WCAG 2.1 AA or WCAG 2.2 AA |
How Does Accessibility Monitoring Work?
At its core, monitoring uses automated scans that crawl pages on a set schedule. Each scan checks the page’s HTML, ARIA attributes, color contrast, form labels, heading structure, and other elements that can be evaluated programmatically.
Results are compared against previous scans. If a new issue appears, the monitoring tool flags it. If an old issue was resolved, it drops off the report. Over weeks and months, this creates a timeline that shows whether conformance is improving, holding steady, or degrading.
Some monitoring services also track specific pages or templates that are high-traffic or high-risk, like checkout flows in ecommerce or enrollment forms in education.
Why Monitoring Matters After an Audit
A WCAG audit evaluates a digital asset at a single point in time. The audit identifies every issue across the pages or screens in scope, and remediation fixes them. But websites are not static. A new blog post, an updated product page, or a redesigned navigation menu can each introduce accessibility issues that were not present during the original evaluation.
Monitoring catches these changes early. Without it, an organization may not discover new issues until the next full audit, which could be months away. By then, the issues have compounded.
For organizations managing ADA compliance or preparing for the European Accessibility Act (EAA), monitoring provides ongoing documentation that demonstrates a sustained commitment to digital accessibility, not a one-time effort.
What Can Monitoring Detect (and What Can It Not)?
Automated scans only flag approximately 25% of issues. That means monitoring is effective at catching things like missing alt text on newly uploaded images, broken heading hierarchies, empty form labels, and insufficient color contrast. These are real, meaningful issues that appear frequently when content is updated.
But monitoring cannot evaluate whether alt text is accurate, whether a custom component is keyboard-operable in practice, or whether a screen reader can correctly interpret a complex data table. Those require human evaluation through a (manual) audit.
The two work together. Monitoring covers the space between audits. Audits cover everything monitoring cannot reach.
Who Needs Accessibility Monitoring?
Any organization that updates its website or app regularly benefits from monitoring. Content-heavy sites like government portals, healthcare platforms, and ecommerce stores are especially good candidates because their pages change frequently.
Organizations subject to Section 508, ADA Title II requirements, or the EAA have a stronger case for monitoring because regulators and procurement teams increasingly expect ongoing conformance documentation, not a dated report.
SaaS companies maintaining an ACR (Accessibility Conformance Report) also benefit. When the product changes, monitoring helps confirm whether the ACR still reflects the current state of the product or whether an updated evaluation is needed.
How Accessible.org Approaches Monitoring
Accessible.org treats monitoring as one piece of a broader accessibility program. The Accessibility Tracker Platform includes scan and monitoring features that let teams track conformance over time, flag regressions, and connect scan results to their audit data.
Monitoring inside the platform is separate from auditing. Scans run on their own schedule. Audit results live in their own workspace. This separation keeps the data clean and prevents confusion between what an automated scan flagged and what a human auditor identified.
For teams managing multiple digital assets or working toward ADA compliance across a portfolio, the platform provides a centralized view of where each project stands.
How Often Should You Monitor?
Frequency depends on how often the asset changes. A brochure site that updates quarterly may need monthly scans. An ecommerce store adding products daily may need weekly scans. A SaaS product shipping features every sprint may need scans tied to each release cycle.
The goal is to catch issues before they accumulate. A scan that runs too infrequently loses its value because the gap between detection and introduction grows too wide.
Monitoring vs. a Full Audit
Monitoring and auditing serve different purposes. An audit is a thorough, (manual) evaluation conducted by an auditor who evaluates every component against the WCAG standard. It is the only way to determine WCAG conformance.
Monitoring is an automated, recurring check that watches for surface-level regressions. It is faster and less expensive per cycle, but it covers less ground.
A strong accessibility program includes both: periodic audits to establish and verify conformance, and ongoing monitoring to maintain it between evaluations.
FAQ
Is accessibility monitoring enough for ADA compliance?
No. Monitoring is a maintenance activity, not a conformance activity. A (manual) audit conducted by a qualified auditor is the only way to determine WCAG conformance. Monitoring helps maintain conformance after an audit and remediation cycle, but it cannot replace the evaluation itself.
What WCAG standard should monitoring scans check against?
Most organizations monitor against WCAG 2.1 AA, which remains the most widely adopted standard. Some are beginning to adopt WCAG 2.2 AA, particularly for new projects or when procurement requirements specify it. The Accessibility Tracker Platform supports both.
Can monitoring generate a VPAT or ACR?
Monitoring data alone cannot produce an ACR. A VPAT is the template, and an ACR is the completed document that reflects a full evaluation. That evaluation requires a (manual) audit. Monitoring data can supplement an ACR by showing ongoing conformance trends, but it does not replace the underlying audit.
Accessibility monitoring is the connective tissue between audits. It keeps the work from losing freshness and gives teams visibility into conformance as their digital assets evolve.
Contact Accessible.org to discuss monitoring, audits, or a complete accessibility program for your organization.
