WAVE vs scheduled accessibility monitoring

WAVE will not email you next Tuesday. Scheduled accessibility monitoring will. That is the whole difference most “WAVE vs [paid tool]” roundups skip.

WAVE is WebAIM’s free accessibility checker: you open a page, run the extension or the web tool, and see icons on failing elements. Scheduled accessibility monitoring is a repeating crawl that stores scores, issues, and a PDF so you do not have to remember to check the site again.

Both are automated. Neither is a human audit. The gap is time and packaging, not magic coverage.

The loop we keep seeing is boring. WAVE finds the unlabeled button during the design sitting. Nobody runs WAVE again after the next plugin update. The failure comes back. Scheduled monitoring is the smoke alarm for that loop.

What WAVE is for

WAVE is the right tool when you are looking at one URL, in one browser, right now.

Designers and developers use it in the same sitting as they change CSS or alt text. In practice, that is still the fastest way to see why a contrast ratio failed: the icon sits on the element, you fix it, you re-run.

The WebAIM Million itself is a WAVE-style pass over the top 1,000,000 home pages. In February 2026 it found detectable WCAG 2 failures on 95.9% of them, up from 94.8% a year earlier. Public failure rates and WAVE results rhyme because they share an engine family.

WAVE does not email you. It does not keep a client-named PDF. It does not record cookies that fired before a consent banner. Asking it to do those jobs is how teams end up with a folder of unlabeled screenshots.

What scheduled monitoring is for

If you own one marketing site, a weekly or monthly recrawl answers a simple question: did we get worse? If you run an agency, the same recrawl is the retainer artifact, a dated pack you can send without rebuilding a screenshot deck.

Seyfarth counted 3,117 federal website accessibility lawsuits in 2025, a 27% jump from 2024 (ADA Title III report). Those filings are not a reason to panic-buy a widget. They are a reason to have a dated record of what you checked after launch, not only at kickoff.

Complience.app’s monitor uses axe-core, not WAVE, plus a pre-consent cookie pass and response headers. Compare the products on WAVE vs Complience.app. Cookie evidence lives on the cookie consent scanner page.

What actually works is treating WAVE as the microscope and the schedule as the calendar. Same class of machine rules. Different job after the page ships.

A practical split

The average home page in the 2026 WebAIM Million carried 56.1 detected errors, 10.1% more than the year before. A one-off WAVE pass will not keep that list from growing after a theme bump.

1. Fix with WAVE or axe in the browser.
2. Confirm with a free Complience.app check.
3. Keep the URL on a schedule if the site still changes.

Do not tell a client that either tool “passed ADA.” Tell them the automated rules that failed, on which pages, on which date.

The W3C is blunt about this: WCAG conformance is a statement about the whole content, not a green badge from one automated checker. Use WAVE to repair. Use a schedule to notice when the repair did not stick.