Accessibility monitoring catches a specific slice of issues that appear between audits: code regressions, new content problems, template drift on recently published pages, and the scan-detectable issues that surface as a site evolves. Monitoring runs continuously through automated scans, so it flags approximately 25% of WCAG issues. It does not replace an audit. It signals where something changed so the team can address it before the next (manual) evaluation.
| Catches | Does Not Catch |
|---|---|
| Missing alt text on new images | Whether existing alt text is meaningful |
| Empty buttons and links | Whether link text describes the destination |
| Color contrast ratios on text | Contrast on text over images or gradients |
| Form fields missing programmatic labels | Whether error messages are clear and associated |
| Document language attribute | Keyboard traps, focus order, screen reader logic |
| Heading structure problems detectable in code | Whether the heading structure reflects the content |
Why Monitoring Exists Between Audits
Websites change. Marketing teams publish new pages, developers ship updates, and product teams release features. Each change can introduce accessibility issues that were not present at the time of the last audit.
A (manual) accessibility audit captures a snapshot of WCAG conformance at a point in time. Monitoring runs continuously in between, scanning for the subset of issues that automated tools can detect.
Accessible.org positions monitoring as a layer that supports the audit cycle, not a replacement for it.
What Does Monitoring Actually Catch?
Monitoring catches issues that have clear, code-level signatures. These are issues a scanner can flag with high confidence because the rule is binary: the attribute is either present or missing, the contrast ratio either passes or does not.
Common items monitoring catches:
Images added without alt attributes. Form inputs missing associated labels. Buttons and links with no accessible name. Color contrast ratios below WCAG thresholds on standard text. Missing or incorrect document language attribute. Duplicate IDs in the DOM. Empty heading elements. Tables missing header markup. iframes missing title attributes.
When a new page is published or a template is updated, these issues often appear first. Monitoring flags them quickly so the team can address them before they spread across the site.
What Monitoring Does Not Catch
Scans only flag approximately 25% of issues. The remaining 75% require human evaluation because the criteria depend on context, meaning, or interaction.
A scanner cannot tell whether alt text is accurate. It cannot determine whether a heading structure reflects the content hierarchy. It cannot evaluate whether a custom widget works with a screen reader, whether focus order makes sense, or whether error messages are clear.
This is the boundary. Monitoring tells you a button has no accessible name. It cannot tell you the button’s accessible name is wrong.
How Monitoring Fits Into the Audit Cycle
The pattern that works for most teams:
- Conduct a (manual) audit to establish a baseline of WCAG conformance.
- Remediate the identified issues.
- Run monitoring continuously to flag scan-detectable regressions and new issues.
- Address monitoring alerts as they appear.
- Conduct another audit when significant changes warrant a fresh evaluation.
Monitoring keeps the work from losing freshness between audits. Without it, scan-detectable issues accumulate quietly until the next audit identifies them all at once.
Template Drift and New Content
Two patterns drive most of what monitoring catches.
Template drift happens when a developer modifies a shared template and accidentally removes an attribute, breaks a label association, or changes a color. The issue then appears on every page using that template. Monitoring catches it quickly because the signature is consistent across many URLs.
New content issues happen when authors publish pages without following the accessibility patterns established during remediation. Images go up without alt text. Buttons get added without accessible names. Headings get skipped. Monitoring flags these on the new pages so the content team can fix them before they compound.
The Role of Real AI in Monitoring
Accessible.org Labs is actively researching how AI can make monitoring and remediation workflows more efficient. The work focuses on grounded, practical applications, where AI supports skilled practitioners reviewing scan output, not claims that AI can automate WCAG conformance.
Real AI in this context means surfacing patterns across monitoring data, grouping related issues, and suggesting remediation paths that a developer can review and apply. The conformance determination still requires human evaluation.
FAQ
Does monitoring replace the need for an audit?
No. Monitoring catches scan-detectable issues, which is roughly a quarter of what WCAG covers. A (manual) audit is the only way to determine WCAG conformance. The two work together. Monitoring keeps the site clean between audits. The audit establishes where conformance stands.
How often should monitoring run?
Continuously, or at least on a recurring schedule that matches how often the site changes. A site that publishes weekly should be monitored weekly at minimum. A site that ships code updates daily benefits from daily scans.
What should a team do with monitoring alerts?
Triage them quickly. Most scan-detectable issues are clear-cut and can be fixed by the team that introduced them. Group similar issues, assign them to the right person, and confirm the fix. The Accessibility Tracker Platform supports this workflow by mapping issues to owners and tracking progress.
Can monitoring catch issues on pages behind authentication?
It depends on the setup. Scans can be configured to access authenticated pages when credentials are provided, though coverage may be more limited than public pages. Discuss scope with the provider before assuming a logged-in flow is being monitored.
Monitoring is a steady signal, not a verdict. It tells the team where something changed so the change can be reviewed and addressed before it grows into a larger issue.
Contact Accessible.org to discuss an audit and monitoring approach for your site.
