Blog 11 · accessibility in UX

95.9% of the web's top home pages failed. Would yours pass?

Pranjal Chawan
Pranjal ChawanUX leader · LinkedIn

Accessibility is the one quality standard that many teams knowingly postpone, then act surprised about.

The WebAIM Million 2026 analysed the top one million home pages. It found detected WCAG 2 failures on 95.9% of them, with an average of 56.1 errors per page. Low-contrast text appeared on 83.9% of pages. Missing form labels appeared on 51%.

These are not exotic problems. Low contrast and unlabelled fields are ordinary design decisions, made every day by people who mean well.

And those numbers are the floor. WebAIM is clear that automated tools cannot detect every failure, and that an absence of detected errors does not prove a page is accessible.

This is now a business issue too

The moral case should be enough. The commercial case is getting harder to ignore.

The Dutch financial regulator's guide to the European Accessibility Act notes that the rules took effect on 28 June 2025 and that consumer banking and financial e-commerce services fall within scope. It puts the number of people living with a disability in Europe at 101 million, or 27% of the population. The same page says that accessible services reach a wider audience and create commercial opportunities.

For banking services, it also describes a requirement that information must not exceed level B2 language complexity. Think about that for a moment. Plain language is now part of the compliance conversation.

Rules vary by country, business size and service, so ask your legal team how they apply to you.

Why accessibility arrives too late

Teams treat it as an audit at the end of a project. By then, colours, components and flows are set, and every fix feels like rework. So it gets pushed to the next release, and then the next.

The fix is to move the decision upstream.

Build it in at the system level

Accessibility scales when it lives in a design system. Fix a component once, and every team using it benefits. In my enterprise work, I have built WCAG-compliant patterns into design systems for automotive and manufacturing clients. That work cut design inconsistencies by 50% in one programme and design redundancy by 40% in another.

Here is the practical order I recommend:

  1. Set the standard. Agree on your target, such as WCAG 2.2 AA, and who owns it.
  2. Fix the foundations. Start with colour contrast, type, focus states, form fields and error messages.
  3. Write it into the definition of done. A feature is not finished until it passes.
  4. Test beyond tools. Use a keyboard. Use a screen reader. Most of all, include disabled people in your research.
  5. Measure and report. Leaders fund what they can see.

Accessible design helps everyone

Clear labels help the user with a screen reader, and they help a tired parent filling in a form on a bus. Good contrast helps someone with low vision, and someone using a phone in bright sun. Accessibility tends to expose design decisions that were not working well for anyone.

Questions people ask

What is accessibility in UX design? It means designing products that people with disabilities can perceive, understand, operate and use independently.

Is passing an automated accessibility test enough? No. Automated tests catch only some issues. You also need manual testing and research with disabled users.

Is accessibility still on your someday list?

You are not alone, and it is easier to start than most teams expect. I would be happy to talk about a sensible first step. Reach me at pranjal.productmind@gmail.com.

© 2026 Pranjal Chawan. All rights reserved.