• WCAG
  • accessibility
  • small business
  • how-to

The 10 Most Common Website Accessibility Problems (and How to Fix Them)

Ten common website accessibility problems, from low contrast to vague link text, with a plain-English fix and a short HTML example for each.

By ComplyKit Team7 min read
On this page

Most website accessibility problems are not exotic. The same handful show up again and again, and many are quick to fix once you know what to look for.

WebAIM runs an annual accessibility analysis of one million website home pages, called the WebAIM Million. In its 2026 WebAIM Million report, 95.9% of home pages had detected WCAG 2 failures, with an average of 56.1 errors per page. The six most common types of detected failures, by share of home pages, were:

  • 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%

This guide covers those six, plus four more common problems that automated tools often can't fully catch. Each comes with a plain-English fix and a tiny before-and-after example you can hand to your web person. The WCAG references are to WCAG 2.1, the benchmark most people use.

This is not legal advice. Fixing these problems makes your site easier to use, but no checklist guarantees compliance or prevents a legal claim. If you have received a demand letter, talk to an attorney.

1. Low contrast text

The problem: Light gray text on a white background, or white text on a pale photo, is hard to read for people with low vision or color blindness, and for anyone on a phone in the sun.

The fix: WCAG 2.1 success criterion 1.4.3 (Level AA) asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Darken the text or lighten the background until it passes.

<!-- Before: light gray on white fails -->
<p style="color: #aaaaaa; background: #ffffff;">Open daily 9 to 5</p>

<!-- After: dark gray on white passes -->
<p style="color: #555555; background: #ffffff;">Open daily 9 to 5</p>

2. Missing alt text on images

The problem: Screen readers can't describe an image unless the code includes a text alternative. Without it, a blind visitor may hear a file name, or nothing at all.

The fix: Add an alt attribute describing what the image shows or does (WCAG 1.1.1, Level A). If an image is purely decorative, use an empty alt="" so screen readers skip it.

<!-- Before -->
<img src="cake-0423.jpg">

<!-- After -->
<img src="cake-0423.jpg" alt="Three-tier vanilla wedding cake with fresh roses">

3. Missing form labels

The problem: If a form field has no label connected to it, a screen reader user doesn't know what to type. Placeholder text that disappears when you start typing is not a reliable label.

The fix: Give every field a visible <label> connected by for and id (WCAG 1.3.1 and 3.3.2, Level A).

<!-- Before -->
<input type="email" placeholder="Email">

<!-- After -->
<label for="email">Email address</label>
<input type="email" id="email" name="email">

The problem: A link with no text, often an icon like a social media logo, is announced as just "link." Visitors can't tell where it goes.

The fix: Give the link an accessible name with visible text or an aria-label (WCAG 2.4.4, Level A).

<!-- Before -->
<a href="https://instagram.com/yourshop"><i class="icon-instagram"></i></a>

<!-- After -->
<a href="https://instagram.com/yourshop" aria-label="Our Instagram">
  <i class="icon-instagram" aria-hidden="true"></i>
</a>

5. Empty buttons

The problem: Same issue as empty links, but for buttons: a search button with only a magnifying glass icon, or a menu button with only three lines.

The fix: Give every button a name (WCAG 4.1.2, Level A).

<!-- Before -->
<button><svg>...</svg></button>

<!-- After -->
<button aria-label="Search"><svg aria-hidden="true">...</svg></button>

6. Missing document language

The problem: If the page doesn't declare its language, a screen reader may read English text with the wrong pronunciation rules.

The fix: Add a lang attribute to the <html> element (WCAG 3.1.1, Level A). This is usually a one-line change in your site's template.

<!-- Before -->
<html>

<!-- After -->
<html lang="en">

7. Keyboard traps and mouse-only controls

The problem: Some people navigate with the Tab key instead of a mouse. If a pop-up, video player, or menu can be entered by keyboard but not exited, they are stuck. The Justice Department's web accessibility guidance lists mouse-only navigation as a common barrier.

The fix: Make sure everything works with a keyboard (WCAG 2.1.1, Level A) and that keyboard focus can always move away (WCAG 2.1.2, Level A). Use real buttons and links rather than clickable div elements, and let the Escape key close pop-ups.

<!-- Before: not reachable or usable by keyboard -->
<div class="close" onclick="closeModal()">X</div>

<!-- After: a real button, reachable with Tab, works with Enter and Space -->
<button type="button" class="close" onclick="closeModal()" aria-label="Close">X</button>

Quick test: Put your mouse away and try to use your homepage with only Tab, Shift+Tab, Enter, and Escape.

The problem: Keyboard and screen reader users may have to move through your entire header menu on every page before reaching the content.

The fix: Add a "Skip to main content" link as the first item on the page (one way to meet WCAG 2.4.1 Bypass Blocks, Level A). It can stay hidden until it receives keyboard focus.

<!-- Before -->
<body>
  <nav>...twenty menu links...</nav>
  <main>...</main>

<!-- After -->
<body>
  <a href="#main" class="skip-link">Skip to main content</a>
  <nav>...twenty menu links...</nav>
  <main id="main">...</main>

9. Headings out of order (or fake headings)

The problem: Screen reader users often jump between headings to scan a page, the way sighted visitors skim. If your "headings" are just bold text, or jump from H1 to H4 for styling, the page structure is lost.

The fix: Use real heading tags in a logical order (WCAG 1.3.1, Level A, and 2.4.6, Level AA). Style them with CSS, not by picking a different heading level.

<!-- Before -->
<p><b>Our Services</b></p>
<h4>Haircuts</h4>

<!-- After -->
<h2>Our Services</h2>
<h3>Haircuts</h3>

These two are different problems, but both are easy wins.

Auto-playing audio or video: Sound that starts on its own can drown out a screen reader. Moving content can distract people with attention or vestibular disorders. If audio plays automatically for more than three seconds, WCAG 1.4.2 (Level A) requires a way to pause or stop it, and WCAG 2.2.2 (Level A) covers moving content. The simplest fix is to not autoplay.

<!-- Before -->
<video src="promo.mp4" autoplay></video>

<!-- After -->
<video src="promo.mp4" controls></video>

Unclear link text: A page full of "click here" and "read more" links is confusing when a screen reader lists links out of context. Make the link text say where it goes (WCAG 2.4.4, Level A).

<!-- Before -->
<a href="/menu">Click here</a> to see our menu.

<!-- After -->
<a href="/menu">See our dinner menu</a>

What a scan can and can't find

An automated scanner is great at finding problems like low contrast, missing alt attributes, missing labels, empty links and buttons, and a missing lang. It is much weaker at judging whether alt text is actually meaningful, whether a pop-up traps keyboard users, or whether link text makes sense. WebAIM's report notes that "not all conformance failures can be automatically detected," and the W3C says human judgment is required. Pair a scan with your own keyboard test and, ideally, a manual review by an accessibility professional.

Want the bigger picture? Read WCAG 2.1 AA explained for small business owners, or learn why overlay widgets aren't a substitute for these fixes.

Find out which of these your site has

Run a free scan of your homepage to see which detectable problems show up, with a plain-English explanation of each.

If you have received an ADA demand letter, start with our guide, Got an ADA Website Demand Letter? What Small Business Owners Should Do First. The Demand Letter Response Kit ($199 one time) adds a full scan of up to 5 pages, a dated PDF report for your attorney, a fix guide, and 30 days of monitoring, then $29/month. Cancel anytime.

See what's on your own site

Run a free automated scan to find common accessibility barriers, with plain-English fixes for each one.