This section of your results translates each finding into the WCAG requirement it breaks. It is the view auditors, procurement teams and lawyers think in.
Reading the table
Each row is one WCAG success criterion that failed on at least one of your pages.
- SC is the criterion's number, such as 1.4.3. The first digit is the principle it belongs to. See WCAG 2.1 AA in plain language.
- Criterion is its name, such as Contrast (Minimum), with the names of the automated tests that failed it listed underneath.
- Instances is the number of affected elements across all your scanned pages.
Click a row to read the requirement's plain description.
Why several issues can share one criterion
A single requirement can be broken in several ways. Info and Relationships (1.3.1), for example, covers form labels, table headers, list markup and more. Each of those is a separate issue in Unique Issues Found, but they all appear under one criterion here.
What this table does not tell you
It only lists criteria that failed an automated test. A criterion missing from this table has not necessarily passed. It may simply be one that automated tests cannot judge. The only complete, criterion by criterion verdict is the one in an Expert Manual Review. See Reading the expert audit.
When to use it
- When someone asks "which WCAG requirements do we fail?"
- When writing or updating an accessibility statement.
- When a contract or tender asks you to report against WCAG criteria.
For planning the actual work, Unique Issues Found is usually more useful, because it is organised by fix rather than by requirement.