Ongoing ADA Website Monitoring
Ongoing ADA website monitoring combines scheduled scans, periodic audits, and internal review processes to track accessibility over time. A single evaluation captures a snapshot. Monitoring captures the trend, identifying when new issues appear and whether previous fixes hold up across updates.
| Key Point | What It Means |
|---|---|
| Scheduled Scans | Automated checks run on a recurring basis (daily, weekly, or monthly) to flag new issues early |
| Scan Coverage | Scans flag approximately 25% of accessibility issues, so they supplement but do not replace human evaluation |
| Periodic Audits | A full (manual) audit conducted at defined intervals catches the remaining 75% of issues that scans miss |
| Key Events | Site redesigns, CMS migrations, and major feature releases should prompt a fresh evaluation cycle |
What Ongoing ADA Website Monitoring Actually Involves
Monitoring is not a single activity. It is a cycle of automated scans, human evaluation, and internal review that repeats on a defined schedule.
Automated scans run against your pages on a recurring cadence. They load each page, evaluate the HTML, CSS, and ARIA attributes, and report deviations from WCAG 2.1 AA success criteria. Because scans only flag approximately 25% of issues, they serve as an early warning system rather than a complete evaluation.
A (manual) audit fills the remaining gap. Auditors conduct screen reader testing, keyboard testing, visual inspection, and code review to identify issues that scans cannot detect. Most organizations schedule a full audit annually or after a significant site update.
Why Websites Drift Out of Conformance
Websites are not static. Content editors add images without proper alt text. Developers push new components that lack keyboard support.
Third-party scripts update without notice. Each change is small on its own. Over weeks and months, they accumulate into WCAG conformance gaps that increase risk under ADA Title III.
Monitoring catches these regressions before they compound.
Setting a Monitoring Schedule
The right cadence depends on how frequently your site changes. A site with daily content updates benefits from weekly scans. A site that changes quarterly may need monthly scans at most.
Pair scans with a full audit at least once per year. If your organization launches a redesign, migrates platforms, or adds a major feature, schedule an audit immediately after deployment rather than waiting for the next annual cycle.
Tracking Issues Between Evaluations
Monitoring produces data. That data is only useful if it connects to a process for fixing what it identifies.
Accessibility compliance platforms allow teams to log issues, assign them to developers, and track remediation progress over time. Scan results feed into the platform automatically, creating a continuous record of what was identified, what was fixed, and what remains open. Without a tracking system, scan results sit in reports that no one acts on.
The Role of Scans in ADA Title III Compliance
ADA Title III does not specify a technical standard for websites. However, the Department of Justice has consistently referenced WCAG as the benchmark for web accessibility. Monitoring against WCAG 2.1 AA through recurring scans and periodic audits is the most direct way to document ongoing effort and reduce legal exposure.
Scans alone do not demonstrate conformance. They demonstrate that an organization is actively checking. A documented monitoring program that pairs scans with (manual) audits and tracked remediation creates a record of sustained commitment to accessibility.
When to Reassess Your Monitoring Approach
Review your monitoring process whenever your site architecture changes significantly. A new CMS, a redesigned checkout flow, or an expansion into authenticated user areas each introduce pages and interactions that existing scan configurations may not cover.
Authenticated pages require a browser extension running within an active session to scan. If your site adds a login portal or member dashboard, your monitoring setup needs to account for those pages separately.
A monitoring program that stays static while the site evolves will miss exactly the areas where new issues are most likely to appear.