Understanding Results
Read a TestKase accessibility scan report — score, severity, WCAG conformance, and per-element detail.
Understanding Results
Every finished scan opens into a report with five layers, from the one-number summary to the exact HTML element that failed.
1. Score and severity summary
The top of the report shows:
- Accessibility score (0–100) computed across all scanned URLs.
- Issue counts by severity: Critical / Serious / Moderate / Minor. See Severity levels for definitions.
- Affected pages and affected components tables, so you can quickly see which URLs and which DOM selectors contribute most of the issues.
Screenshot (TODO): Summary panel with score, severity pills, affected pages/components tables
2. WCAG conformance matrix
A grid of every WCAG criterion relevant to the version you scanned, marked pass, fail, or incomplete (needs review). Click any failing criterion to jump straight to its issues. See WCAG conformance matrix.
3. Issue list
Grouped by rule (e.g., color-contrast, image-alt) or by WCAG criterion (e.g., 1.1.1 Non-text Content). Use the dropdown at the top of the list to switch grouping. Filter by severity, WCAG level, or category.
Each group shows the rule description, impact, count of matching issues, pages affected, and a roll-up component count.
4. Issue detail panel
Click any issue to open the detail panel:
- Rule ID and human-readable description (e.g., "Images must have alternate text").
- Failure summary — why this element failed.
- Impact — critical / serious / moderate / minor.
- WCAG tags, criterion, and level — with a link to the W3C quickref.
- Target selector — CSS path to the failing element.
- All matching targets on the same page.
- HTML snippet — the exact failing markup.
- Bounding box — element position, used to highlight it in the page snapshot.
Screenshot (TODO): Issue detail panel with rule, selector, HTML snippet, and WCAG tags
Full details: Issue details.
5. Page snapshots with element inspection
Each scanned URL stores an HTML snapshot. Click an issue to highlight the failing element in the snapshot with a red outline; zoom, pan, and fit-to-container controls help you find small elements. See Element inspection.
Hiding issues
Triaged an issue as a false positive or an accepted risk? Use the hide toggle on an issue to remove it from the active list. Hidden issues are excluded from the accessibility score, so the number reflects only what you're still acting on. You can unhide at any time.
Exports
From the report header you can export the full report as a PDF — ideal for stakeholder sharing, audits, and compliance attestations. A scan-run history CSV is also available for tracking scores over time. See Export formats.
🚧 Coming soon — per-issue CSV and machine-readable JSON exports for programmatic consumption. Today, report export is PDF (plus the scan-run history CSV).
Interpreting "incomplete" results
An issue flagged "incomplete" is one axe-core couldn't decide automatically and flagged for manual review (for example, ensuring a button is keyboard-reachable when its handler isn't statically analyzable). Disable the Needs review toggle at scan time if you only want hard violations.