Fix guides · accessibility

How to fix common website accessibility errors

By · 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:

FailureShare of home pages
Low contrast text83.9%
Missing alternative text for images53.1%
Missing form input labels51%
Empty links46.3%
Empty buttons30.6%
Missing document language13.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

Images and icons

Links and buttons

Forms

Page structure

ARIA attributes

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.

Run the free checkno sign up · one page at a time

Rather have someone fix it for you? Tell me about your site.