Managing Scans
Browse, filter, re-run, share, and delete scans from the Website Scanner list.
The Website Scanner list (/web-scanner) is the hub for every scan in your workspace.
It shows two kinds of scans together:
- Scans made with the Website Scanner.
- Reports saved from the Chrome extension (Chrome Toolkit).
⚠️ Deleting a scan is permanent. It removes the scan, every run it has ever produced, all issues and page results, the stored page snapshots, and any team shares — immediately and in one step. There is no trash, no undo, and no recovery window. If you only want a schedule to stop firing, pause the schedule instead of deleting the scan.
The scan list
The list shows one row per scan, not one row per run. Each row shows:
- Scan name, with the first URL beneath it (
+N morewhen the scan has several) - Score, issue count and status
- Last run — when the scan last ran, or
not run yet - Type — Web Scanner or Chrome extension
The score, issues, status and date describe the scan's most recent run, not the scan's own first run. A scan that runs daily shows today's result once today's run finishes. This matters for scheduled scans, which never run at the moment you create them: their row would otherwise stay empty for life while their runs happened out of sight.
A scan that repeats also carries a line under its name saying so — how often, when it is next due, and which run number it is on, e.g. Daily · 9:10 AM IST · next Tomorrow at 9:10 AM IST · Run #4. Times are shown in the schedule's timezone, not yours.
Searching, filtering and sorting follow the same values you can see. Filtering by Completed finds a scheduled scan whose latest run completed, and sorting by score orders by the score on the row.
In the All scans tab two more columns appear: Created By and Teams (the accessibility teams the scan is shared with).
The browser and OS the scan ran on — e.g. 151.0.7922.34 (Device Farm · Windows 11) — is recorded on the report, not in the list.
Scope filters
Use the scope tabs at the top of the list:
- All scans — the leftmost tab: every scan visible to you (your scans + any scan shared with an accessibility team you belong to).
- My scans — scans you created. This is the tab the page opens on, even though All scans sits to its left.
- Scheduled — only scans that repeat, within whichever of the two scopes you last had selected. Only Website Scanner scans appear here, because Chrome extension reports can't be scheduled. See The Scheduled tab.
Search and filter
- Search — free-text match on scan name.
- Status filter — narrow to Pending / Running / Completed / Failed. It matches the status shown on the row (the latest run), not the scan's own status, so filtering by
Completedfinds a scheduled scan whose latest run completed. - Date ranges — filter by created-at or updated-at windows.
- Team filter — show scans shared with specific accessibility teams.
- Type — in the Filters window, show only Web Scanner scans or only Chrome extension reports.
- Sort — by name, score, total issues, status, or created date; ascending or descending.
Row actions
Click the row to open the report (only once the scan has finished or failed). The ⋯ menu adds:
- Share with team — creator only. See Sharing scans.
- Scan history — every run of this scan, with scores and deltas. See Scan history.
- Run scan — runs the same URLs, WCAG version, rule toggles, and auth config again, as a new run in the history. Creator only. One run at a time: the action is greyed out whenever the scan itself reads
RunningorPending, and a run started while another one is still going is refused with "A scan is already running. Please wait for it to complete." - Edit configuration — change the name, URLs, rule settings, or schedule. Creator only. Unlike the New Scan form, this dialog enforces the 10-URL cap as you go: it shows a
N/10 pagescounter and disables Add at 10, so you cannot save a list the scan would refuse. - Clone configuration — opens the New Scan form carrying this scan's scan settings and schedule: WCAG version, rule toggles, page-load delay, browser/OS, and the recurrence if it has one (cadence, time, day of week / day of month). It does not carry the URLs, the name, or the authentication config — add those yourself. Names must be unique across your scans, so a clone cannot reuse the original's name. The schedule's timezone is not cloned: the copy takes the timezone from your own profile, so a scan set to 09:10 in Asia/Kolkata becomes 09:10 in your zone. Check the Next scan line before saving.
- Delete scan — permanent and immediate. Deleting a scan removes the scan, all of its scheduled and manual re-runs, every issue and page result, the stored page snapshots, and any team shares. There is no trash and no undo. Only the person who created the scan can delete it.
Chrome extension rows
Click a Chrome extension row to open its report. Its ⋯ menu is shorter:
- Open report
- Share with team
- Delete
These reports have no history, and you can't run, edit or clone them. You also can't tick them to compare or combine with other scans.
The Scheduled tab
Web Scanner → Scheduled lists every scan that repeats, in one place, so you do not have to open scans one at a time to find out what is running on its own.
It adds two columns:
- Next run — when it is next due, in the schedule's timezone
- On — a switch that pauses or resumes the schedule
Pausing is not deleting. The scan, its history and the schedule's settings all stay; resuming needs no retyping. Only Delete scan removes anything, and that is permanent.
A schedule stops on the scan's own 90th day. The schedule lives on the scan's row, and that row is removed by the 90-day retention sweep like any other. When it goes the schedule goes with it, silently — no warning email, no notification, and the scan disappears from the list. Pausing does not pause that clock. If you need a recurring scan to keep running past 90 days, create a fresh scan before the original ages out. See Data retention.
Resuming a schedule needs an Automate plan. If you do not have one the switch refuses and tells you why, rather than appearing to work and quietly failing later.
To change when a scan runs, use Edit configuration → Schedule.
Trigger — manual vs scheduled
Every run is either manual (you ran it yourself) or scheduled (the platform ran it automatically on a recurring cadence you configured).
The two kinds draw on different plans: manual scans need your org's Live Browser plan (or its free minutes) and scheduled scans need an Automate plan (or its free minutes) — scheduling is automation. If the Automate plan lapses, scheduled runs are recorded as failed with a clear message and the schedule stays in place; runs resume once a plan is active again. See Scan limits.
Every run — the first one, your manual re-runs, and every scheduled run — is listed inside the scan, under Scan history. Scheduled runs never appear as their own rows in the scan list.
| Where | What you see |
|---|---|
| Scan list | One row per scan: name, score, issues, status, date, and (in All scans) creator and teams |
| Scan → Scan history | One row per run: run number (#1, #2, …), date, a Manual or Scheduled badge, score, issue count, score delta, status, author |
Open Scan history from the row's ⋯ menu, or from the Scan history tab inside the report.
Configure a schedule when you create a scan, or later with Edit configuration → Schedule. Switch Enable recurring scans on and pick:
| Cadence | You also pick | Notes |
|---|---|---|
| Daily | Time of day | |
| Weekly | Day of the week, time of day | |
| Monthly | Day of the month, time of day | The list runs 1st–28th only, so a monthly scan can never skip a February |
Every schedule also carries its own timezone, and the dialog shows the resulting Next scan date and time as you change the fields, so you can check it before saving.
In the API this is scheduleConfig: enabled, cadence (daily / weekly / monthly), time (HH:mm), timezone (IANA), plus dayOfWeek (0 = Sunday … 6 = Saturday) for weekly and dayOfMonth for monthly. The API accepts a dayOfMonth of 29, 30 or 31 that the dialog will not offer — use 28 or lower unless you are sure what you want in a short month.
TestKase checks for due schedules every few minutes and creates a fresh run each time one comes round. One sweep starts at most 50 due runs, so a large backlog drains over several sweeps, oldest first, rather than landing on the fleet at once.
A run that is still going holds its own scan's schedule: no scheduled run starts while a run of that scan is running. A run wedged in running therefore stops that scan repeating until it clears — if a daily scan has no new runs, open Scan history and check whether the last one ever finished.
A run starts within a few minutes of its scheduled time rather than on the exact second. If a run is ever missed — a maintenance window, say — the schedule picks up again at its next slot; it does not fire the missed runs back to back.
A scan created with a schedule does not run straight away. It waits for its first scheduled slot and shows as pending until then, so setting up a daily 09:10 scan at 09:06 gives you one run — at 09:10. A scan created without a schedule runs immediately.
⚠️ A scan created with its schedule already on cannot be run by hand. The scan itself stays at pending for its whole life — only its runs complete — and Run scan is greyed out on anything pending. If you want a result now and a recurring one, create the scan without a schedule so it runs immediately, then add the schedule with Edit configuration → Schedule. That scan keeps its Run scan action.
The timezone defaults to your profile timezone but belongs to the schedule, not to you. Changing your profile timezone later will not move a scan that is already scheduled — so a scan set to run at 9am local traffic-low time keeps running then, even if you travel or update your profile. To move it, edit the scan's schedule directly.
To pause a schedule: flip the On switch in the Scheduled tab, or open the scan → Edit configuration → Schedule → switch Enable recurring scans off. Either way the scan and its history stay; nothing new fires.
To stop entirely: delete the scan. That deletes the schedule and every run it has ever produced — use the pause toggle instead if you want to keep the history.
Status lifecycle
running → completed
↘ failed- pending — created with a schedule and waiting for its first slot. A scan you run yourself never sits here.
- running — the scan is waiting for a Device Farm browser, or actively scanning. A scan you run yourself goes straight to
running; there is no queue to watch. - completed — all URLs finished; the report is viewable.
- failed — the scan could not finish. Hover the badge for the reason (most often an unreachable URL, an HTTP error status, a login failure, or no free scan browser). See Troubleshooting.
Scan history
Scan history is the full record of one scan: every run, in order, with what changed between them.
- Stat cards and a score-over-time chart across the runs.
- One row per run — run number (
#1,#2, …), date, a Manual or Scheduled badge, score, issue count, score delta, status, author. - Search by run and filter by status (completed / failed / running / pending); the list paginates.
- Export CSV — the whole history, or just the runs you tick.
- Compare — tick exactly two runs. See Comparing & consolidating.
- Delete — tick runs and delete them. This removes those runs and their results permanently, exactly like deleting a scan; the scan itself and its other runs stay. Run
#1cannot be deleted here — the button greys out with "Base version cannot be deleted from here", because it is the scan. Delete the scan itself if that is what you want.
Pagination
The list paginates in batches. Large workspaces can scroll through hundreds of scans without loading every page at once.
Comparing and consolidating reports
Once you have more than one scan, two extra report views unlock:
- Compare — diff two runs of the same scan to verify a fix or track a regression.
- Consolidate — merge multiple independent scans into one combined report (with PDF export) for audits or executive review.
See Comparing & Consolidating Scans.