Accessibility lets anyone use your site, including with a screen reader or a keyboard only, and in many sectors it is already a legal requirement. Checking it page by page with a browser extension does not scale.
With rendering enabled, AD2SPIDER runs axe-core on every page and groups the results by WCAG level (A, AA and AAA), best practices and checks that need manual review, with the affected elements and the explanation of each rule.
WCAG accessibility errors
They stop the page from working or being indexed properly. Fix them first.
Accessibility: WCAG level A violations
- Why it matters
- The page violates WCAG level A criteria, the minimum: some content cannot be used by some people (images without alt text, unlabelled forms, missing language…).
- How to fix it
- Fix each listed rule on the affected elements; axe's help explains how.
Accessibility: WCAG level AA violations
- Why it matters
- The page violates WCAG level AA criteria, the level most regulations require (in the EU, the European Accessibility Act via EN 301 549): insufficient contrast, blocked zoom…
- How to fix it
- Fix each listed rule on the affected elements.
WCAG accessibility warnings
Real problems worth fixing.
Accessibility: WCAG level AAA violations
- Why it matters
- The page violates WCAG level AAA criteria, the strictest level (enhanced contrast, among others). Few sites fully meet it.
- How to fix it
- Consider fixing them if your audience or sector requires it.
Accessibility: best practices not followed
- Why it matters
- The page does not follow accessibility best practices outside WCAG (heading order, landmarks, content outside regions…).
- How to fix it
- Review the listed rules; they often improve structure for search engines too.
WCAG accessibility information
Data to understand the site; not errors in themselves.
Accessibility: checks needing manual review
- Why it matters
- axe cannot decide these checks on its own (for example, contrast over background images): they need a look.
- How to fix it
- Review the listed elements.