Fix common axe-core accessibility errors
Short, practical pages for the rule IDs developers paste from automated accessibility scans. Each guide explains the impact, WCAG mapping, failing markup, fixed code, and what still needs human review.
Fix color-contrast axe errors
Text does not have enough contrast against its background for many low-vision users to read it comfortably.
Fix image-alt axe errors
An image is missing an alternative text decision, so screen reader users may lose information or hear a raw filename.
Fix label axe errors
A form control has no programmatic label, so assistive technology cannot announce what input is expected.
Fix button-name axe errors
A button has no accessible name, so assistive technology users cannot tell what action it performs.
Fix link-name axe errors
A link has no accessible name, making its destination or purpose unclear to assistive technology users.
Fix aria-required-attr axe errors
An ARIA role is missing attributes required for that role, so the component may be exposed incorrectly.
Fix html-has-lang axe errors
The page does not declare its default language, so screen readers may choose the wrong pronunciation rules.
Fix document-title axe errors
The document has no useful title, making browser tabs, history, and assistive navigation harder to understand.
Fix meta-viewport axe errors
The viewport configuration can block zooming or responsive layout, making content harder to read on mobile.
Fix aria-valid-attr axe errors
An ARIA attribute is misspelled or invalid, so browsers and assistive technology may ignore it.