How to fix common website accessibility errors
By Justin Zagar · Updated
Each page below takes one error that accessibility checkers report, in the checker’s own words, and explains it plainly: what it means, who it affects, how to find it and how to fix it, with small before and after code and the steps in common website builders.
The six most common failures
WebAIM checks the home pages of the top million websites every year. In its February 2026 run, 95.9% had at least one detected WCAG failure. These were the six most common kinds:
| Failure | Share of home pages |
|---|---|
| Low contrast text | 83.9% |
| Missing alternative text for images | 53.1% |
| Missing form input labels | 51% |
| Empty links | 46.3% |
| Empty buttons | 30.6% |
| Missing document language | 13.5% |
Source: WebAIM, The WebAIM Million, 2026 report, checked November 8, 2026. WebAIM uses its own WAVE tool, so its names differ a little from axe’s rule names below.
Every fix guide
Text you can read
- Elements must meet minimum color contrast ratio thresholds
Low color contrast ·
color-contrast· WCAG 1.4.3 - Zooming and scaling must not be disabled
Zoom turned off ·
meta-viewport· WCAG 1.4.4
Images and icons
- Images must have alternative text
Images without alt text ·
image-alt· WCAG 1.1.1 - Image buttons must have alternative text
Image buttons without alt text ·
input-image-alt· WCAG 1.1.1, 4.1.2 - <svg> elements with an img or image role must have alternative text
SVG images without alt text ·
svg-img-alt· WCAG 1.1.1
Links and buttons
- Links must have discernible text
Links with no text ·
link-name· WCAG 2.4.4, 4.1.2 - Buttons must have discernible text
Buttons with no text ·
button-name· WCAG 4.1.2 - Elements must have their visible text as part of their accessible name
Visible text doesn't match the name ·
label-content-name-mismatch· WCAG 2.5.3
Forms
- Form elements must have labels
Form fields without labels ·
label· WCAG 4.1.2 - Select element must have an accessible name
Dropdowns without labels ·
select-name· WCAG 4.1.2
Page structure
- <html> element must have a lang attribute
No page language set ·
html-has-lang· WCAG 3.1.1 - Documents must have <title> element to aid in navigation
Page has no title ·
document-title· WCAG 2.4.2 - Frames must have an accessible name
Embeds without a title ·
frame-title· WCAG 4.1.2 - <ul> and <ol> must only directly contain <li>, <script> or <template> elements
Broken list markup ·
list· WCAG 1.3.1
ARIA attributes
- ARIA hidden element must not be focusable or contain focusable elements
Hidden content you can still tab to ·
aria-hidden-focus· WCAG 4.1.2 - Elements must only use permitted ARIA attributes
ARIA attributes where they aren't allowed ·
aria-prohibited-attr· WCAG 4.1.2 - Required ARIA attributes must be provided
ARIA roles missing required attributes ·
aria-required-attr· WCAG 4.1.2 - ARIA attributes must conform to valid values
ARIA attributes with bad values ·
aria-valid-attr-value· WCAG 4.1.2
What a scanner can and can’t tell you
Fixing this clears one automated check. It doesn’t mean the page is accessible, and it doesn’t settle any legal question. Automated tests catch only part of the problems. W3C puts it plainly: evaluation tools “can not determine accessibility, they can only assist in doing so.” The rest takes a person working through the site with a keyboard and a screen reader.
Source: W3C WAI, Selecting Web Accessibility Evaluation Tools. Not legal advice.
Check a page for free
Scan any page of your site against WCAG 2.1 AA in about 30 seconds. You get the problems automated testing finds, in plain words, with a link to a fix guide for the common ones.
Rather have someone fix it for you? Tell me about your site.