Quick Start: Accessibility Testing

Scan a page for WCAG issues in under two minutes.

Step 1 — Open the Website Scanner

1. Go to accessibility.testkase.com.
2. Click Website Scanner in the sidebar.
3. Click New Scan (top-right).

Step 2 — Add a URL

1. Type the URL you want to scan (protocol auto-added if missing).
2. Press Enter or click Add page.
3. Repeat to add more — up to 10 URLs per scan.
4. The scan name is auto-filled from the first URL's domain; edit if you want.

Step 3 — (Optional) Adjust scan settings

Click the ⚙ gear next to Add page.

• Scan version — defaults to WCAG 2.1 AA (the most common compliance target). Pick any WCAG 2.0 / 2.1 / 2.2 × A / AA / AAA combination.
• Advanced rules / Best practices / Needs review — three toggles for rule packs; defaults are fine for a first run.
• Authentication — switch to the Authentication tab if your URLs are behind a login. Three methods are supported: Cookies, Login Form, HTTP Headers. See Authenticated scanning.

Click Done.

Step 4 — Start the scan

Click Create Scan. The scan appears in your list with status pending → running → completed. Typical runtime: 30–90 seconds per URL.

Step 5 — Read the report

Click the scan row once it's complete. The report has five layers:

1. Accessibility score (0–100) with severity breakdown (Critical / Serious / Moderate / Minor).
2. WCAG conformance matrix — pass / fail / incomplete per criterion.
3. Issue list — grouped by rule or by WCAG criterion; filterable.
4. Issue detail — rule, failure summary, WCAG tags, target selector, HTML snippet.
5. Page snapshot — failing element highlighted in a red outline.

Severity Levels

Full definitions: Severity levels.

What to explore next

• Accessibility Overview — features at a glance.
• Web Scanner — all scan-time options.
• Authenticated scanning — scan pages behind a login.
• Workflow Analyzer — catch issues that only appear mid-flow.
• Chrome Toolkit — free DevTools extension for one-click scans.