The six accessibility failures that also cost you leads

Tuan Nguyen·May 5, 2026
The six accessibility failures that also cost you leads

Six accessibility failures have topped WebAIM's annual report for seven years running. All six are cheap to fix, and all six are quietly costing you bookings from customers who have no disability at all.

Every February, WebAIM scans the home pages of the top one million websites and counts the accessibility errors a machine can detect. They have done this eight years running. The same six problems have topped the list for seven of them.

Seven years. Same six. Nobody is fixing them.

That is worth sitting with for a second, because none of the six is difficult. They are not architectural problems or budget problems. They are small, boring, and cheap, and they are also, almost exactly, the things that quietly cost you bookings from customers who have no disability at all.

What the 2026 numbers actually say

The 2026 WebAIM Million report found detectable WCAG failures on 95.9 percent of the home pages it scanned, up from 94.8 percent the year before. That is the first increase in six years. The average page carried 56.1 detected errors, up about ten percent in twelve months.

The reason things went backwards is not that people stopped caring. It is that pages got heavier. Home pages have nearly doubled in element count since 2019, and more code means more places to get it wrong.

Here is the part that matters for a small business. Six categories account for 96 percent of every error found.

  • Low contrast text, on 83.9 percent of pages
  • Missing alt text on images, 53.1 percent
  • Form inputs with no label, 51 percent
  • Links with no text in them, 46.3 percent
  • Buttons with no text in them, 30.6 percent
  • No language set on the document, 13.5 percent

One honest caveat, because it changes how you should read those figures. Automated scanning catches somewhere around a third of real WCAG problems. The rest need a person. So 95.9 percent is not the ceiling. It is the floor.

Why this shows up in your booking numbers

You will find plenty of articles claiming accessible sites convert twenty percent better, usually attributed to some official sounding body. I went looking for the source of that particular number and could not find one. It gets cited blog to blog, and the trail runs cold. So I am not going to hand it to you.

What I will hand you is the mechanism, which you can check on your own site in ten minutes.

Take low contrast text, the most common failure by a wide margin. Pale grey on white looks refined on a designer's calibrated monitor in a dim room. Now put it on a five year old phone, at half brightness, held at arm's length in a car park in Houston in July. Your prices are on that page. So are your hours. If someone squints at it for four seconds and leaves, that never appears in your analytics as an accessibility failure. It appears as a bounce.

Or take unlabelled form fields, on more than half of all pages. A missing label breaks a screen reader completely. It also breaks your browser's autofill, because the browser has no idea that the box wants a phone number. So every visitor types their details by hand on a phone keyboard. Some of them stop halfway.

Empty links and empty buttons are usually an icon with no text inside it. A screen reader announces it as nothing at all. Google's crawler gets the same nothing, which is why these failures tend to travel with weak search visibility rather than causing it.

None of these are accessibility problems that happen to hurt business. They are the same defect, seen from two angles.

The ten minute version

You do not need an audit or a consultant to find out where you stand. Run your home page and your booking page through WAVE, the free tool WebAIM uses for the report itself. It runs in the browser and returns the same six categories.

Then do the three checks a tool cannot do for you. Open your site on your own phone, outdoors, in daylight, and try to read the prices. Fill in your own booking form using only the keyboard, no mouse. And turn the volume up and let your phone's built in screen reader read the page while you look away.

That third one is uncomfortable the first time. It is also the fastest way to understand what a chunk of your visitors are working with.

Where the overlay widgets fit

You may have been sold a script that promises to make your site accessible overnight. Be careful with those.

UsableNet counted 4,928 US web accessibility lawsuits filed in 2025, and roughly a fifth of the ones filed in the first half of that year were against sites that already had an overlay installed. The widget did not stop the claim. Fixing the six things in the actual page does.

The fix is not glamorous and it does not need a rebuild. Darken your body text. Write alt text on the images that carry meaning and leave the decorative ones empty. Put a real label on every form field. Put words inside your icon buttons, even if they are visually hidden. Set the language attribute once.

An afternoon of work, roughly, on a site of normal size. It has sat undone on 95.9 percent of the web for seven years, which tells you something about how many businesses are competing with you on this particular front.

So pick up your phone, walk outside, and open your own booking page.

Can you read it?

Tags

usabilityaccessibilitylead generationweb design

Written by

Tuan Nguyen

Web Designer & Developer · Houston, TX

Founder of Ideavezy LLC and a full-stack developer with 20+ years of experience. He builds custom, mobile-first websites for salons, spas, restaurants, and local businesses across Houston and Texas — no templates, no page builders.

Book a free audit call
Six accessibility failures that also cost you leads | Ideavezy