Skip to content
Velloreth
Web Development 9 min read

Web Accessibility: The 20% That Fixes 80% of Issues

Six failure types account for 96% of detected accessibility errors — contrast, alt text, labels, empty links and buttons, and document language.

By

Accessibility advice usually arrives as a wall of guidelines: WCAG has hundreds of success criteria, and the number of ways to get it wrong appears endless.

The data says otherwise. WebAIM’s annual analysis of the top one million home pages (the 2026 report, run in February) found an average of 56.1 detectable accessibility errors per page — and six error types account for 96% of all detected errors, a list that has not changed in seven years. Fix those six and you have eliminated almost everything machines can see.

That does not make a site accessible. Automated tools detect a subset of problems; the rest require judgment, keyboard testing, and screen reader time. But it does mean the path from “terrible” to “solid baseline” is short and well-mapped.

The numbers, for context

Error type% of home pages affected (2026)
Low contrast text83.9%
Missing alternative text on images53.1%
Missing form input labels51.0%
Empty links46.3%
Empty buttons30.6%
Missing document language13.5%

2026’s report also found that 95.9% of home pages had at least one detectable WCAG 2 failure — up from 94.8% in 2025, reversing six years of gradual improvement. Pages keep getting heavier (average element counts have nearly doubled in seven years), and complexity outruns remediation.

Two adjacent findings are worth keeping in mind as you read the fixes below. Only 17.1% of home pages had a skip link, and 41.8% skipped heading levels. And pages using ARIA averaged 59.1 errors versus 42 on pages without it — correlation, not causation (ARIA-heavy pages are heavier across the board), but a useful warning that ARIA is not a retrofit that fixes things by itself.

1. Low contrast text

The most common failure by a wide margin, and the most mechanical to fix.

The rule (WCAG 2 AA):

  • Normal text: 4.5:1 contrast ratio against its background.
  • Large text (≥24px, or ≥18.66px bold): 3:1.
  • UI components and graphical objects — icons, input borders, focus indicators: 3:1 (SC 1.4.11).

Where it goes wrong:

/* the usual suspects */
.meta      { color: #999; }        /* on white: ~2.85:1 — fails */
.placeholder { color: #bbb; }
.disabled  { color: #888; }

Muted gray metadata is the single biggest offender, and it is almost always a design-system decision rather than an oversight — which means the fix belongs in the design system, one token change, instead of a sweep across components.

How to fix it in practice:

  • Check ratios with your browser’s contrast picker or a dedicated tool before shipping a new color token.
  • Darken text or lighten backgrounds until the ratio clears; on dark themes, lighten the muted colors — the same hex value does not carry over.
  • Never encode state in color alone (SC 1.4.1). An invalid field needs an icon and text, not just a red border. The same applies to links inside paragraphs — underline them.
  • Test your focus indicator too. Removing outlines without a replacement is a 1.4.11 failure.

2. Missing alternative text

More than half of home pages ship images with no alt at all. The fix is mostly a policy decision you make once:

<!-- decorative: announce nothing -->
<img src="divider.svg" alt="" />

<!-- informative: describe the content, not the file -->
<img src="chart.png" alt="Revenue by quarter: Q1 $1.2M, Q2 $1.4M, Q3 $1.1M, Q4 $1.9M" />

<!-- linked image: the alt is the link's accessible name -->
<a href="/posts/css-grid">
  <img src="grid-cover.png" alt="CSS Grid: a practical guide" />
</a>

<!-- complex image: short alt plus a longer description nearby -->
<figure>
  <img src="architecture.png" alt="System architecture: three services behind a load balancer" />
  <figcaption>
    Clients hit the load balancer, which routes to the API service;
    the API reads from Postgres and enqueues work for the worker.
  </figcaption>
</figure>

Rules that cover most cases:

  • Empty alt="" for decorative images. Omitting the attribute is not the same thing — a missing alt makes screen readers announce the filename, which is noise.
  • Never write “image of…” or “photo of…”. The role is already announced.
  • Do not paste the caption verbatim into alt text; screen reader users hear both.
  • Write alt text for the function. A logo in the header links home — its alt should be the site name, not a description of the logo’s colors.
  • For charts, describe the data. “Bar chart” tells a screen reader user nothing; the numbers are the content.

CMS-driven sites fail here by the volume of unmanaged uploads. If your platform lets editors add images without an alt field, make the field required — even requiring “decorative” as an explicit choice beats an empty default.

3. Missing form labels

Half of home pages have inputs with no associated label. The pattern:

<!-- wrong: placeholder is not a label -->
<input type="email" placeholder="Email address" />

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

<!-- right, and labeled hint/error wiring -->
<label for="email">Email address</label>
<input
  id="email"
  name="email"
  type="email"
  autocomplete="email"
  aria-describedby="email-hint"
/>
<p id="email-hint">We'll send the receipt here.</p>

Why placeholders are not labels: they disappear on focus, they have contrast problems by design, and users forget what a field was asking by the time they finish typing. A visible label is the accessible name; the placeholder is a hint at best.

Also: aria-label works when a visible label genuinely cannot exist (icon-only controls), but a visible label is better — aria-label can disagree with visible text, which fails WCAG 2.5.3 (label in name).

46.3% of home pages have links with no accessible text. The classic cases:

<!-- icon-only link, no name -->
<a href="/settings"><svg>…</svg></a>

<!-- "read more" repeated fifty times -->
<a href="/post/1">Read more</a>

Fixes:

<!-- give the link a name -->
<a href="/settings" aria-label="Settings"><svg aria-hidden="true" …>…</svg></a>

<!-- or include visually hidden text -->
<a href="/settings"><svg aria-hidden="true" …>…</svg><span class="visually-hidden">Settings</span></a>

<!-- make link text distinguishable -->
<a href="/post/1">Read more about CSS grid</a>

Mark decorative SVGs aria-hidden="true" so their internal <title> does not fight the accessible name you set on the link.

The “read more” problem is not cosmetic: screen reader users often navigate by pulling up a list of links on the page. Fifty links all labeled “Read more” is a useless list.

5. Empty buttons

30.6% of pages have buttons whose only content is an icon without a name. Same fix as links, different role:

<button type="button" aria-label="Close dialog">
  <svg aria-hidden="true" …>…</svg>
</button>

One subtlety: role="button" on a <div> does not give you keyboard activation, focus, or the expected AT announcements for free. Use a real <button>; style away its defaults with CSS if needed. The same goes for links styled as buttons — an <a> without href is not in the tab order and is announced as static text.

6. Missing document language

The cheapest fix on the list, affecting 13.5% of pages:

<html lang="en">

Without it, screen readers may use the wrong pronunciation rules — an English page read with a French voice is largely unintelligible. Mark language changes within the page too:

<p>The term <span lang="de">Doppelgänger</span> entered English in the 19th century.</p>

Beyond the six: four cheap wins

The six cover what automated tools detect most often. These four are nearly free and cover what keyboard users hit first:

Heading order. One h1 per page matching the page’s main topic; do not skip levels (h2 → h4) to get a smaller font — that is what CSS is for. Screen reader users navigate by headings more than by any other mechanism.

Landmarks and a skip link. Wrap main content in <main>, give repeated navigation <nav aria-label="…">, and put a skip link first in the DOM:

<body>
  <a class="skip-link" href="#main">Skip to content</a>
  <header>…</header>
  <main id="main" tabindex="-1">…</main>
</body>

Only 17.1% of home pages ship a skip link; on any site with a large header, it is the difference between one tab press and forty.

Visible focus. :focus-visible styles that meet the 3:1 non-text contrast requirement. If you remove default outlines, replace them — do not skip them.

Autocomplete attributes. autocomplete="email", "name", "street-address" and friends let browsers and password managers fill fields correctly. This is SC 1.3.5 (identify input purpose) at AA, and it measurably reduces input errors on mobile.

ARIA: first, do no harm

The 2026 finding — pages with ARIA averaging more errors than pages without — does not mean ARIA causes failures. It does confirm a rule worth following religiously:

No ARIA is better than bad ARIA.

<!-- wrong: div soup with roles bolted on -->
<div role="button" class="btn" onclick="…">Save</div>

<!-- right -->
<button type="button" class="btn">Save</button>

The first version needs role, tabindex, a keydown handler for Enter and Space, and correct focus styling — all of which the native <button> already provides. Reach for ARIA when HTML has no equivalent (role="status" for a live announcement, aria-expanded on a disclosure), and test every ARIA addition with a screen reader, because the failure mode of ARIA is confident nonsense announced to the people who rely on it most.

Testing that actually catches things

A realistic workflow for a team that does not have an accessibility specialist:

  1. Automated scan on every page type. axe DevTools, Lighthouse, or WAVE in CI or during review. Treat the results as a floor: WebAIM itself notes that absence of detected errors does not indicate an accessible page.
  2. Keyboard pass, every release. Unplug the mouse. Tab through the page: can you reach everything, in a sensible order, with a visible focus ring? Can you operate menus, dialogs, and forms? Can you reach and use the skip link?
  3. One screen reader session per significant feature. VoiceOver (macOS/iOS), NVDA (Windows), or Narrator. You are not certifying anything — you are checking that names, roles, and announcements match what you intended.
  4. Contrast check on new color tokens, not on every element. Fix it at the design-system level.
  5. Real content, not lorem ipsum. Long German words, short labels, empty states, and 200% zoom all expose problems that placeholder text hides.

The short version

If you do nothing else: check your contrast ratios, label every input, give every image a deliberate alt (empty or descriptive — the choice is yours, absence is not), name every icon-only control, set lang, and tab through your page before you call it done.

Six fixes. Most of what is detectable, gone. The rest of accessibility — real keyboard operation, meaningful structure, understandable content — is slower work, but it starts from a baseline that almost nobody has, and those six are how you get there.