Accessibility finding
An accessibility failure, graded by how many scanners report it
Accessibility Error Severity: High
Part of the audit Automated WCAG rules. Finding id: accessibility.scannerAgreement.
What it costs you
People who rely on assistive technology cannot use this part of the page.
What to do
Follow the scanner's guidance for this rule: [help url]
What it checks
- Missing names or labels
- Wrong roles or states
- Page structure and regions wrong
- Not reachable with the keyboard
- Keyboard position not visible
- Language of the page problems
- Table problems
- Form and error message problems
- Link purpose unclear
- Repeated IDs confusing screen readers
- Page breaks when zoomed
- Buttons and links too small
How to fix it
Fix the element the scanners agree on
- Open [help url] for the rule.
- Fix it in the template or component that prints [selector], so every page that uses it is fixed.
How to check: Run the scanners on the page again: no scanner reports the element.
A real case
When the UK Government Digital Service planted 142 accessibility barriers on a test page, the best of 13 automated tools found 40% of them and the worst found 13%.
Thresholds
| Name | Default | Meaning |
|---|---|---|
min_scanners | 2 | How many scanners must report the same element and success criterion before the finding counts as a failure. |