Scheduled scans run on their own in the background, so accessibility does not depend on someone remembering to check. They run server-side against your published pages and populate your reports.
How they work
Turn scheduled scans on in Settings and choose a daily or weekly cadence. The plugin fetches your own published URLs and checks their HTML, then stores each run in History with a per-page breakdown.
Server-side checks are HTML-only
Scheduled scans use HTML-only checks. They do not run the full in-browser engine, so they do not replace builder-time scans or manual verification. Think of them as a stable baseline and an early warning for drift.
What they are good for
- Catching new issues that appear after content edits
- Giving you a repeatable history for QA and client review
- Feeding the regression tracking so you can see trends
Tip
There is no third-party accessibility service and no tracking. Scheduled scans only fetch your own published URLs to check their HTML.
Was this page helpful?Thanks for the feedback!