Test Scheduling - Sitemap (Overview)

Test Scheduling helps teams run recurring Accessibility scans on websites and web apps without manually starting a new scan every time.

When you want recurring Accessibility scans outside of Web Scanner, this overview explains how the native scheduling flow fits the product, how it differs from Web Scanner, and where to go for setup, URL import, authentication, and recurring schedules. Use it to orient sitemap-based or crawler-driven workflows and ongoing visibility into accessibility drift.

Use this when

you want recurring scans
you want to import or discover many URLs at once
you need scheduled visibility into accessibility drift over time

Product boundary

This page is for the Accessibility-native scheduling flow. If you use the separate Web Scanner product instead, start from Getting Started with Web Scanner or Starting an Accessibility Scan with Web Scanner.

Typical workflow

Create the scheduled scan.
Add URLs manually, through CSV, or through sitemap extraction.
Add saved login configurations (or tunnel / local access) if required—see Login & Authentication for Scheduled Scans.
Set the schedule.
Review the resulting reports.

Onboarding: schedule your first recurring scan

Read Steps to Schedule an Accessibility Scan end-to-end once—menus use the same vocabulary as the live product.
Seed URLs using Sitemap Extraction & URL Import when you have more than a handful of pages.
If pages sit behind login, open Add login configurations in Advanced options or use dashboard Login configurations, then attach a profile—see Login & Authentication for Scheduled Scans (Basic, Form, Multi-page, or tunnel per your environment) before widening scope.
Start with a weekly cadence on a subset of URLs; promote to daily only after noise is manageable.
After the first run, open Navigating the Dashboard and confirm aggregates match expectations.
Optional: enable Fragment Identifier in DevTools settings when hash routes should split reporting for SPA teams (web URL grouping only).