Accessibility TestingScans
Scans
Three ways to scan — Website Scanner, Authenticated Scanning, and Workflow Analyzer.
Scans
TestKase Accessibility offers three scan modes, all sharing the same WCAG rule engine, report format, and workspace:
| Mode | What it scans | Best for |
|---|---|---|
| Website Scanner | Up to 10 URLs in a single run | Public pages and authenticated pages that load on a direct URL |
| Authenticated Scanning | Pages behind login (cookies / login form / HTTP headers) | Dashboards, admin pages, customer portals |
| Workflow Analyzer | Recorded user flows | Issues that only appear after interaction (form fills, navigation, state changes) |
All three produce the same report shape: score, severity breakdown, WCAG conformance matrix, issue list with element detail.
Choosing the right mode
- Everything should start with Website Scanner. If your target page loads on a URL and shows the same content on every load, Website Scanner is the fastest path to a report.
- Use Authenticated Scanning when the page is inside a login wall and the URL alone can't reach it. You still get a Website Scanner–style report, just with credentials applied first.
- Use Workflow Analyzer when the bug appears only after user action — e.g., a validation error state, a modal that opens, a page that reveals content after form interaction.
Limits shared across all modes
- Up to 10 URLs per scan (Website Scanner and Authenticated Scanning).
- No cap on the number of scans per workspace.
- Retention and export formats depend on your plan — see Scan limits.