Summary & Score
Interpret the score, severity counts, and affected-pages/components tables at the top of a scan report.
Summary & Score
The summary panel at the top of a scan report gives you the one-screen health check.
Accessibility score (0–100)
A composite score across all scanned URLs. Higher is better. The score is weighted by severity — one critical issue hurts your score more than several minor ones.
Rough reading of the number:
- 90–100 — conformant or near-conformant with your chosen WCAG target.
- 70–89 — a few serious or moderate issues. Usually fixable in a single pass.
- < 70 — systemic gaps; prioritize critical and serious findings first.
The score is a guide, not a compliance verdict. Legal conformance claims should reference the WCAG conformance matrix, not the score.
Severity breakdown
Four pills summarize the issue counts:
| Pill | What it means |
|---|---|
| Critical | Blocks users with disabilities from core functionality |
| Serious | Major barrier; most users affected can work around it with effort |
| Moderate | Usability issue; shouldn't block |
| Minor | Polish item; rarely user-blocking |
Click any pill to filter the issue list to that severity. Full definitions: Severity levels.
Affected pages table
Lists every URL scanned with:
- Issue count per URL
- Score per URL
- Link to jump to that URL's subset of issues
Use this to prioritize — one URL with many critical issues often outweighs ten URLs with polish items.
Affected components table
Shows DOM selectors that appear repeatedly across issues. A single bad component (e.g., a reusable Button with poor contrast) often explains dozens of individual issues. Fix the component once; the entire report improves.
Each row includes:
- Selector — CSS path to the component.
- Count — how many issues reference this selector across the scan.
- HTML snippet — the failing markup (hover or click to expand).
What's not in the summary
- Per-element details — those live in the issue detail panel. See Issue details.
- Historical trends — the current report is a point-in-time snapshot. Re-scan on a schedule to track trends.