Skip to main content
A scan loads each page of a surface in a real browser on Ility’s servers and runs automated accessibility checks against it. Members and owners can start scans. Viewers can watch them.

Start a scan

There are several ways to start a scan, depending on what you want to check. Scans use the surface’s settings: its WCAG target and its enabled engines. Excluded pages are skipped. If scheduled scanning is turned on for a surface, Ility also scans it automatically once a week.
A surface can only have one surface-wide scan running at a time. If you choose Run scan while one is in progress, Ility tells you and leaves the running scan alone. Rescanning a page or re-checking an issue can run alongside it.

Follow progress

While a scan runs, the surface header shows how many pages are done. Results appear as each page finishes, so you don’t have to wait for the whole scan.
  • Scans in the sidebar lists every scan in the workspace, newest first. Filter it by status, and open a scan to see each page’s result.
  • Activity shows scans and crawls as they happen across all your surfaces.
A scan moves through these statuses:

Pause, resume, or cancel

While a scan runs, the surface header shows Pause scan and Cancel in place of Run scan. A paused scan shows Resume scan. Cancel asks you to confirm first.

When a page fails

Sometimes a single page can’t be scanned. The scan carries on with the other pages and records why that page failed. Common reasons:
If your site blocks unfamiliar traffic with a firewall or bot protection, pages may fail with rate limiting or HTTP errors. Allow Ility’s crawler through. See About IlityBot.

Compare two scans

On a surface’s Overview, choose Compare scans in the scan history to see what changed between two scans. Issues are sorted into three columns:
  • Disappeared: found in the earlier scan and not in the later one.
  • Persisted: found in both.
  • Appeared: new in the later scan.