Accessibility audit
Run axe-core's rules on the page, grouped by impact, each linked to its elements and how to fix it.
Run it#
- Turn Nitpique on, open the side panel, choose Page, then Accessibility.
- Choose the Full audit card. The audit runs then, and again when you press Rescan.
- Four tiles count the elements that fail, by impact: Critical, Serious, Moderate and Minor.
Reading the results#
The rules that failed are grouped by impact, worst first, and within a group the rule that found the most elements comes first. Open a rule to see what it asks, the WCAG criteria it belongs to, and every element it found with what to fix. Hover an element to outline it on the page; click it to select it. How to fix opens the rule's page in Deque University, and Copy as issue copies the rule and its elements as Markdown.
Needs review, folded at the foot, lists what the rules could not decide on their own, such as text over an image. Check those by hand. The Report menu copies or downloads the whole audit.
How it works#
The rules are axe-core's, by Deque Systems, the engine many accessibility tools use. It runs in the page, in Nitpique's own space, so the page's scripts never see it, and nothing is sent anywhere. axe-core is large, so it is loaded only when you open the audit, not when Nitpique turns on.
Questions
What runs the audit?
axe-core, by Deque Systems, in the page itself. It is loaded only when you open the audit, and nothing is sent anywhere.
Does a clean audit mean the page is accessible?
No. Automated rules find part of what WCAG asks; the rest, such as whether alt text says the right thing, needs a person.