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.

Step 1 — Open the Website Scanner

1. Go to accessibility.testkase.com.
2. From the sidebar, click Website Scanner.
3. Click the New website scan button in the top right. (The form it opens is headed New Scan.)

Step 2 — Add a URL

1. Type a URL into the input (example.com/ works; protocol is auto-added).
2. Press Enter or click Add page.
3. The URL appears in the list below. You can add up to 10.

The scan name is auto-suggested from the first URL's domain (example.com-1, example.com-2, …). Edit it if you want a more descriptive label — but a name has to be one you haven't used before, or the scan is refused with "Scan name … already exists".

In a hurry with a longer list? Upload CSV takes one URL per line and Add sitemap pulls URLs off the site itself — just trim back to 10 before you submit, because neither stops you at the cap. See Adding URLs in bulk.

Step 3 — (Optional) Pick a browser & adjust settings

The Run on picker chooses the real desktop browser your scan runs on — Chrome, Firefox, or Safari engine (WebKit), on Windows or macOS, any installed version. The default Chrome · Windows · Latest is fine for a first scan. (Manual scans use your Live Browser plan or its 15 free lifetime minutes.)

Click Scan Settings — the labelled button on the row above the URL input, to the right of Enter page URL — to open the settings dialog.

• 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.

Step 4 — Start the scan

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

If you belong to more than one organization, check you are in your primary one (the first you joined) before you start — a scan created anywhere else fails with "Scans can only run in your primary organization for now."

The scan starts as running — there is no separate queued state — and finishes as completed or failed. It first waits for a free browser from the fleet (up to 100 seconds), then loads and scans each URL in turn, so a multi-URL scan can take a few minutes. See Scan limits.

Step 5 — Open the report

When the row shows completed, click it.

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

1. Accessibility score (0–100) and a severity breakdown.
2. Where you stand — how many criteria we were able to check for your chosen WCAG version, which ones are failing, and how many need a person because no automated rule covers them.
3. Issue list, grouped by rule or by WCAG criterion.
4. Issue detail when you click a single issue — rule description, failure summary, HTML snippet, target selector.
5. Page snapshot with the failing element highlighted in a red outline — visible to the person who created the scan; team-shared viewers get the report without it.

Step 6 — Export or share

From the report header:

• Export the report as a PDF or a CSV — both are summaries, without the per-issue detail (a separate scan-run history CSV is available from the Scan history tab).
• Share with team — if you've created an accessibility team, share the scan for team members to view.

Full details:

• Export formats
• Sharing scans

What to do next

• Run a scan against a page behind a login — see Authenticated scanning.
• Catch issues that only appear during an interaction by recording a flow with the Chrome Toolkit and reading it in the Workflow Analyzer — see Workflow analyzer.
• Install the free Chrome Toolkit for one-click scans from DevTools — see Chrome Toolkit.