What a finding is, what verdicts mean, and how findings are documented.
What a finding is
A finding is the auditor's evaluation of one criterion on one sample. Each (sample, criterion) pair has at most one finding.
Verdicts
| Verdict | Meaning |
|---|---|
| Compliance | The sample meets the criterion |
| Failure | The sample does not meet the criterion |
| Not applicable | The criterion does not apply to this sample (no matching content) |
| Not tested | The criterion has not yet been evaluated |
| Not auditable | The criterion cannot be evaluated reliably (e.g., requires hardware not available) |
Only Failure verdicts produce visible issues in the report and statement.
Finding fields
- Verdict (required)
- Problem description — what is wrong, observable, in plain language
- Solution suggestion — how to fix it, code-referenced when possible
- Screenshots (one or more)
- Notes (free text)
- Linked criterion (filled automatically)
- Source (manual / scanner-suggested / extension-suggested)
Why both problem and solution
The accessibility statement and the report draw on these fields. A good problem description tells the user what is wrong; the solution tells them how to fix it. See methodology / finding quality.
Where findings are edited
- Finding editor (full view) on the audit's Findings tab.
- Inline within the audit grid (compact view).
Scanner-pre-filled findings
If the scanner add-on is active, automated axe-core results pre-fill problem and solution fields where they map cleanly to a criterion. The auditor always validates or overrides. See integrations and procedures / use the scanner.
Related
- methodology / finding quality — what makes a good finding.
- audits, samples.