What Actually Breaks: The 6 WCAG Failures Behind Most Accessibility Claims

When someone tells you their website is "accessible," it is worth asking how they know. Because when researchers actually measure accessibility at scale, the results are stark — and remarkably consistent. WebAIM's annual analysis of the top one million homepages has found for years running that roughly 95% of home pages have detectable WCAG failures.

But here is the useful part: the failures are not random. A small number of issue types account for the overwhelming majority of what breaks. If you understand these six, you understand where almost every "we're compliant" claim quietly falls apart — and you know exactly what a real scan should be looking for.

1. Low-contrast text — the most common failure by far

Found on roughly 79% of home pages. This is the single most widespread accessibility problem on the web.

What it is: text that does not stand out enough from its background. Light gray on white, white on a pale photo, a brand color that looks fine to a designer but fails the math.

Why it matters: people with low vision — a large and growing group — literally cannot read it. WCAG requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.

Why it hides: it usually looks fine to the person who built the page. It is invisible to the naked eye and obvious to a tool. That gap is exactly why "it looks fine to us" is not a compliance standard.

2. Missing alternative text for images

Found on roughly 56% of home pages.

What it is: an image with no alt text, so a screen reader has nothing to announce — or announces a meaningless filename.

Why it matters: a blind user gets silence, or "IMG_4821.jpg," where a sighted user gets information. If the image is a button, a chart, or a logo that links somewhere, the user is simply stuck.

The fix: meaningful images get concise, descriptive alt text; purely decorative images get marked empty so screen readers skip them. Both halves matter.

3. Missing form input labels

Found on roughly 48% of home pages.

What it is: a form field with no programmatically associated label. A visible placeholder is not a label — it disappears when you start typing, and assistive technology often ignores it.

Why it matters: forms are where the real damage happens. A search box, a login, a contact form, a checkout, a patient-intake form — if a screen-reader user cannot tell what a field wants, they cannot complete the task at all. This is the failure most likely to turn into a lost customer, a missed appointment, or a legal complaint.

4. Empty links

Found on roughly 45% of home pages.

What it is: a link with no discernible text — often an icon or image link with no accessible name.

Why it matters: a screen reader announces "link" with nothing after it. The user has no idea where it goes. Navigation built out of empty links is navigation that does not work.

The fix: every link needs a real, descriptive accessible name — and "click here" or "read more" repeated twenty times is only marginally better than empty.

5. Empty buttons

Found on roughly 30% of home pages.

What it is: the same problem as empty links, applied to buttons — a control with no accessible name. Common with icon-only buttons (a hamburger menu, a close "X," a search magnifier).

Why it matters: the user knows there is a button but not what it does. Closing a modal, opening a menu, submitting a form — all become guesswork.

6. Missing document language

Found on roughly 16% of home pages.

What it is: the page does not declare what human language it is written in (the lang attribute).

Why it matters: screen readers use this to choose the correct pronunciation engine. Without it, an English page may be read aloud with the wrong accent and phonetics — turning content into gibberish. It is a one-line fix that is skipped astonishingly often.

What these six have in common

Two things stand out.

First, they are predictable. Because the same handful of issues drive most violations, a competent scan finds them reliably. There is no mystery about where sites break.

Second — and this is the crucial part — most of them are invisible to the person who built the page. Low contrast looks fine. A missing label looks fine. An empty icon button looks fine. Everything *looks* fine, which is exactly why so many organizations sincerely believe their site is accessible when it is not. The page renders perfectly for someone using a mouse and good eyesight, and fails completely for someone who is not.

That is the trap behind most "we're compliant" claims. It is not usually dishonesty — it is that no one measured the things you cannot see by looking.

The good news

Because these failures are this concentrated and this well-understood, they are identifiable in a scan and fixable by people who know what they are looking for. A site that fails all six today can be genuinely conformant in far less time, and for far less money, than most organizations expect — once someone actually finds the problems.

The starting point is never a redesign. It is a measurement.

See what's actually on your pages

You do not have to guess whether your site has these six failures — they are detectable. The honest first move is a complete scan that shows you what is really there, page by page, so a "we're accessible" claim can be replaced with evidence.

Sources: WebAIM Million — Annual Accessibility Analysis of the Top 1,000,000 Home Pages; Web Content Accessibility Guidelines (WCAG) 2.1. Percentages reflect WebAIM's most recent published analysis and shift modestly year to year. This article is informational and is not legal advice.