Six errors cause 96% of the accessibility failures detected on the web: low-contrast text, missing image alt text, unlabeled form fields, empty links, empty buttons, and a missing page language. That’s the finding of WebAIM’s February 2026 analysis of one million home pages, and it matches what we see every week when we scan real small-business sites. The same short list, over and over.
That is unusually good news. It means the problem is not a thousand mysterious defects — it’s a half-dozen specific, fixable mistakes. This post walks through each one: what it looks like on an actual small-business site, who it blocks, and the exact fix.
Six errors cause 96% of the problem
According to the WebAIM Million, 95.9% of home pages had detectable WCAG failures in 2026, averaging 56.1 errors per page. Nearly all of those errors fall into six categories:
| Error | % of home pages (WebAIM, Feb 2026) | WCAG success criterion |
|---|---|---|
| Low-contrast text | 83.9% | 1.4.3 Contrast (Minimum) |
| Missing image alt text | 53.1% | 1.1.1 Non-text Content |
| Missing form input labels | 51% | 3.3.2 Labels or Instructions |
| Empty links | 46.3% | 2.4.4 Link Purpose (In Context) |
| Empty buttons | 30.6% | 4.1.2 Name, Role, Value |
| Missing document language | 13.5% | 3.1.1 Language of Page |
One note before the fixes: these numbers come from automated detection, which is exactly why they’re so consistent. Machines are good at finding these six. They are bad at finding broken keyboard access, illogical focus order, and misleading link context — so treat this list as the floor of your problem, not the ceiling.
What is the most common website accessibility issue?
Low-contrast text — light gray body copy on white, pale placeholder text, white text over a busy hero photo. WebAIM found it on 83.9% of home pages in 2026 — more than any other error, in a report that notes the same six categories have dominated for seven consecutive years.
It blocks more people than owners expect: users with low vision, older customers, anyone reading a phone in sunlight. And it’s usually a theme default, not a deliberate choice. The trendy “soft gray” that shipped with your template often measures under 3:1 against white.
The fix. WCAG 1.4.3 requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (18pt, or 14pt bold). Paste your text and background colors into our color contrast checker — if a pair fails, darken the text or lighten the background until it passes. Because most contrast failures live in one or two theme styles, a single CSS change typically fixes hundreds of reported errors. Our color contrast guide covers the edge cases, like text over images.
Missing alt text on images
More than half of home pages — 53.1% in WebAIM’s 2026 data — have images with no alternative text. Without it, a screen reader announces “image” or reads out a filename like IMG_4032.jpg, and a blind customer gets nothing.
On the small-business sites we scan, the repeat offenders are predictable: hero and slider images inserted by page builders, product photos uploaded in bulk, and logos linked to the homepage with no text at all.
The fix. Every meaningful image needs an alt attribute that says what the image communicates — “Woman fitting a hearing aid in a clinic,” not “image123.” Purely decorative images should get an empty alt="" so screen readers skip them; the W3C’s alt decision tree walks you through which is which in about a minute per image. Most CMS platforms expose an alt text field right in the media library, so this one rarely needs a developer. Our alt text guide shows worked examples by image type.
Form fields with no labels
Half of home pages (51%) have form inputs with no programmatic label. This is the error with the most direct revenue cost, because forms are where visitors become customers: quote requests, bookings, checkout, newsletter signups.
The classic small-business version is the placeholder-only form. The field says “Email address” in gray text inside the box — but that’s a placeholder, not a label. It vanishes the moment someone types, and many screen readers never associate it with the field at all. A blind user tabs into your contact form and hears “edit text, blank.”
The fix. Every input needs a visible <label> element connected to it in the code (via for/id), or an equivalent accessible name. Keep the label visible above the field rather than relying on placeholders — sighted users with memory or attention issues need it too. This satisfies WCAG 3.3.2, and our accessible forms guide covers error messages and required-field markup while you’re in there.
Empty links and empty buttons
Two flavors of the same failure: an interactive element with no name. WebAIM found empty links on 46.3% of home pages and empty buttons on 30.6%. A screen reader user lands on one and hears just “link” or “button” — a door with no sign on it.
You almost certainly have these if your site uses icon-only controls: the magnifying-glass search button, the hamburger menu, the shopping-cart icon, and the row of social media icons in your footer. Visually they’re obvious. In the code, many are empty.
The fix. Give every link and button a text name. If the control is an icon, add an aria-label (“Search,” “Open menu,” “Cart, 2 items”) or visually hidden text. This is WCAG 4.1.2 Name, Role, Value territory — and a caution: sprinkling ARIA around without understanding it makes things worse. WebAIM’s 2026 report found that home pages with ARIA averaged 59.1 errors versus 42 on pages without it. We wrote about why in ARIA: the most misused tool in accessibility.
Missing page language
The quiet one: 13.5% of home pages never declare what language they’re written in. Screen readers use that declaration to pick a pronunciation engine. Without it, software may read your English page with the wrong speech rules, turning your content into audible mush for the user.
The fix. One attribute on one line: <html lang="en">. It satisfies WCAG 3.1.1, takes a developer under a minute, and clears the error site-wide. If parts of a page are in another language — a Spanish tagline, say — mark those sections too. There is no cheaper accessibility fix on this list.
What we actually see on small-business sites
The WebAIM Million measures the whole web. Run those same checks against typical U.S. small-business sites — as our free scanner does — and the same six errors show up, but with a distinct local flavor.
Small-business sites are built from templates, page builders, and plugins, so errors arrive in clusters. A restaurant site has a low-contrast theme and an unlabeled reservation widget and a PDF-only menu. A dental practice has icon-only phone and map links and a placeholder-only appointment form. The third-party embeds — booking tools, chat widgets, review carousels — are frequently the worst offenders, and they’re the parts owners can’t see into.
The upside of template-driven sites cuts both ways, though: because one template defect repeats on every page, one code fix repairs every page. We routinely see a scan’s error count drop by three-quarters after fixing fewer than ten distinct defects. That’s the difference between this list and a generic ADA compliance checklist — the checklist tells you everything to verify; field data tells you where your problems almost certainly are.
How to fix accessibility errors, in order
Work the list in order of user impact and effort:
- Declare the page language. One line, site-wide fix, do it today.
- Fix your theme’s text colors. Test them with a contrast checker and adjust the stylesheet — the highest error count usually falls to the fewest code changes.
- Name your icon links and buttons. Search, menu, cart, social icons — every control gets an accessible name.
- Label every form field with a real, visible label. Prioritize checkout and contact forms; they carry your revenue.
- Write alt text for meaningful images and empty
alt=""for decorative ones, starting with your most-visited pages. - Then test what machines can’t. Run the ten-minute keyboard test, because automated scans miss entire categories of barriers — and those are the ones plaintiffs’ testers find with a real screen reader.
That last step matters legally. A clean automated report is progress, not proof: the six errors above are simply the ones machines can count. The barriers that show up in demand letters — keyboard traps, broken focus, forms that fail silently — take human testing, which is why real ADA website compliance work pairs scans with manual review.
Find out which ones your site has
You now know what the six most common accessibility issues are and how to fix them. The only question left is which ones are on your site — and guessing is slower than checking. Run a free accessibility scan and you’ll get the specific errors, on your actual pages, mapped to the fixes above. If the report is longer than you want to handle in-house, our remediation service fixes the real code — no widgets, no shortcuts.