Accessibility rules, explained

Every finding in a Reviseberg report carries a rule id – color-contrast, image-alt, keyboard:trap. Each rule below has its own page: what fails, who it affects, why it usually happens, and how to fix it, with code that has been run against the same check before it was published.

Two engines report these rules. axe-core is the open-source rules engine our crawler runs on every page; its rule ids are the ones a CI pipeline or a browser extension shows too. The keyboard agent is ours: it walks a journey on your site with real key presses and reports what no rules engine can see, such as a focus nobody can see or a trap nobody can leave.

What a rule can and cannot tell you

A rule answers one narrow question. image-alt finds an image with no text alternative; it cannot tell a good description from IMG_2231.jpg. So a rule that passes is not a success criterion that passes: most WCAG criteria need a person to finish the job, and our WCAG 2.2 reference says for each criterion how far automated checks get.

Some rules are best practice: axe-core maps them to no WCAG success criterion. They are real obstacles – content outside landmarks, a skipped heading level – and Reviseberg reports them, but never as a WCAG failure and never in a compliance report.

Run these rules on your own site