Reference
Every check we run, and what to do when it fails
75 checks map to a WCAG success criterion. Another 30 are good practice that no criterion requires — we report them separately so a compliance conversation stays about compliance.
Powered by axe-core 4.13.0 · © Deque Systems, MPL-2.0
ARIA
Colour
Forms
Keyboard
Language
moderatehtml-xml-lang-mismatchHTML elements with lang and xml:lang must have the same base language3.1.1
Name, role, value
seriousaria-hidden-focusARIA hidden element must not be focusable or contain focusable elements4.1.2
Parsing
Semantics
seriouslabel-content-name-mismatchElements must have their visible text as part of their accessible name2.5.3
Sensory and visual cues
Structure
Tables
criticaltd-has-headerNon-empty <td> elements in larger <table> must have an associated table header1.3.1
serioustable-fake-captionData or header cells must not be used to give caption to a data table.1.3.1
serioustd-headers-attrTable cell headers attributes must refer to other <th> elements in the same table1.3.1
Text alternatives
Time and media
Best practice, not conformance
These catch real problems, but failing one does not fail WCAG. They are off by default on scheduled scans so your score means what it says.
moderatelandmark-banner-is-top-levelBanner landmark should not be contained in another landmarkadvice
moderatelandmark-contentinfo-is-top-levelContentinfo landmark should not be contained in another landmarkadvice
moderatelandmark-no-duplicate-contentinfoDocument should not have more than one contentinfo landmarkadvice
moderatelandmark-uniqueLandmarks should have a unique role or role/label/title (i.e. accessible name) combinationadvice
minorpresentation-role-conflictElements marked as presentational should be consistently ignoredadvice