Accessibility TestingReference
Overview
Reference pages for accessibility scanning — WCAG versions and levels, severity labels, rule categories, and troubleshooting.
Concept-level reference for TestKase Accessibility. Use these pages when you need to know what a setting or a label in a report actually means, or when a scan didn't do what you expected.
In this section
- WCAG levels and versions — what WCAG 2.0, 2.1 and 2.2 each added, what Levels A, AA and AAA mean, every value in the Scan Settings dropdown, and guidance on which combination to pick. Scans default to WCAG 2.1 AA.
- Severity levels — the four impact buckets on every issue (critical, serious, moderate, minor), what each one implies, how to triage with them, and what they deliberately don't tell you. Also explains why the API calls this field
impact. - Rule categories — what the Advanced rules, Best practices and Needs review toggles in Scan Settings actually turn on or off, their defaults, the full 23-rule Advanced list, and which rules always run regardless.
- Troubleshooting — why a scan says
Pending(and when that is normal), reports that come back empty, a score that dropped on its own, the common scan-failure messages, reports that have aged out, Compare and Consolidate refusals, Chrome Toolkit panel problems, misaligned or missing element highlights, and export questions.
Where to start
- Choosing a standard before your first scan → WCAG levels and versions.
- Reading a report you've just received → Severity levels.
- Tuning what a scan reports on → Rule categories.
- Something went wrong → Troubleshooting.
