Warning

axe-core found more problems

The short version

Fix the listed rules.

What it means

With colour contrast turned on, we also run axe-core, an open-source accessibility engine, in our browser. This finding lists the rules it reported that our own basic checks don't already cover, such as lists that contain the wrong elements, ARIA attributes with invalid values, or controls hidden from assistive software. The detail names each rule; the result shows example elements.

Why it matters

Each rule maps to a WCAG 2 success criterion. A rule marked serious or critical usually blocks some people from using part of the page, for example a control that a screen reader can't reach. Others make the page harder to use without stopping anyone.

How to fix it

  1. Open the axe-core section of the result and expand each rule.
  2. Read the rule's short description and look at the example elements.
  3. Look up the rule by its id in the axe-core rule list (on the Deque website) for a fuller explanation and code examples.
  4. Fix serious and critical rules first.
  5. Fix the shared component or template, not each page, so the fix reaches every page.

Check it worked

Run the accessibility check again with colour contrast turned on. The rules you fixed should be gone from the list. Automated checks find only some problems, so also test the page with the keyboard and a screen reader.