Walk through creating, running, and reading your first accessibility scan end-to-end.

Your First Scan

This is the 5-minute end-to-end walkthrough. You'll create a scan, wait for it to finish, and interpret the report.

Prerequisites

A TestKase account with access to the Accessibility product. (Sign up at testkase.com if you don't have one.)
A public URL you want to scan. A known-accessible site works great for a demo — try your own marketing page.

Screenshot (TODO): Website Scanner list with New Scan button highlighted

The scan name is auto-suggested from the first URL's domain. Edit it if you want a more descriptive label.

Click the ⚙ gear icon next to Add page to open Scan Settings.

Scan version — defaults to WCAG 2.1 AA. Change it if you need to test against a different standard.
Advanced rules — leave on (default).
Best practices — leave off unless you want non-WCAG UX checks.
Needs review — leave on to catch items that require manual verification.
Authentication — skip for now; see Authenticated scanning when you're ready.

Click Done to close settings.

Click Create Scan. You'll see a toast confirming the scan is queued, and the browser redirects you to the scan list.

The scan status progresses: pending → running → completed. One URL typically takes 30–90 seconds.

When the row shows completed, click it.

The report has five layers — top-down, from summary to element detail:

Accessibility score (0–100) and a severity breakdown.
WCAG conformance matrix — pass / fail / incomplete per criterion.
Issue list, grouped by rule or by WCAG criterion.
Issue detail when you click a single issue — rule description, failure summary, HTML snippet, target selector.
Page snapshot with the failing element highlighted in a red outline.

Screenshot (TODO): Completed report with score, severity pills, and issue list

From the report header:

Export as PDF, CSV, or JSON.
Share with team — if you've created an accessibility team, share the scan for team members to see and comment.

Full details:

Run a scan against a page behind a login — see Authenticated scanning.
Try the Workflow Analyzer to catch issues that only appear during an interaction — see Workflow analyzer.
Install the free Chrome Toolkit for one-click scans from DevTools — see Chrome Toolkit.