WCAGdesk
WCAG 2.2 AA · axe-core · BFSG / EN 301 549

How to fix the accessibility issues axe-core finds

Each check our scanner reports, explained and mapped to WCAG 2.2, EN 301 549 and the German BFSG — with concrete fixes and code. Start with a free scan to see which apply to your site.

axe-core ruleWCAG 2.2Category
color-contrastWCAG 1.4.3 Contrast (Minimum) (AA)Color & Contrast
image-altWCAG 1.1.1 Non-text Content (A)Images & Alt
link-nameWCAG 2.4.4 Link Purpose (In Context) (A)Links & Navigation
labelWCAG 4.1.2 Name, Role, Value (A)Forms & Labels
html-has-langWCAG 3.1.1 Language of Page (A)Language
document-titleWCAG 2.4.2 Page Titled (A)Structure & Landmarks
button-nameWCAG 4.1.2 Name, Role, Value (A)Forms & Labels
select-nameWCAG 4.1.2 Name, Role, Value (A)Forms & Labels
frame-titleWCAG 2.4.1 Bypass Blocks / Page Titled (A)Structure & Landmarks
heading-orderWCAG 1.3.1 Info and Relationships (A)Structure & Landmarks
empty-headingWCAG 1.3.1 Info and Relationships (A)Structure & Landmarks
listWCAG 1.3.1 Info and Relationships (A)Structure & Landmarks
bypassWCAG 2.4.1 Bypass Blocks (A)Keyboard & Focus
meta-viewportWCAG 1.4.4 Resize Text (AA)Zoom & Reflow
regionWCAG 1.3.1 Info and Relationships (A)Structure & Landmarks
aria-required-attrWCAG 4.1.2 Name, Role, Value (A)ARIA
aria-valid-attr-valueWCAG 4.1.2 Name, Role, Value (A)ARIA
th-has-data-cellsWCAG 1.3.1 Info and Relationships (A)Structure & Landmarks

More checks added regularly. axe-core covers roughly 30–40% of WCAG automatically — see our methodology.