Web Accessibility: The Audience You're Quietly Turning Away

An inaccessible site quietly turns away customers, and increasingly, invites legal risk. Here's what web accessibility actually means, what WCAG asks for, and the practical fixes that matter most.

Around one in five people has a disability, and if your site is hard to use with a keyboard, a screen reader, or low vision, you're quietly turning a slice of them away, along with the sale. Most of it is invisible to you: nobody emails to say "I couldn't check out because the button wasn't reachable." They just leave.

Web accessibility isn't a niche compliance chore, it's making sure everyone can actually use what you built, and it happens to improve SEO, usability, and legal safety at the same time. This guide covers what accessibility really means, what WCAG asks for, and the practical fixes that move the needle.

What is web accessibility (and WCAG)?

Web accessibility means designing and building your site so people with disabilities, visual, motor, auditory, or cognitive, can perceive, navigate, and use it. In practice that covers everything from sufficient colour contrast and keyboard navigation to alt text for images, captions for video, labels on form fields, and a logical heading structure. The global standard is WCAG (Web Content Accessibility Guidelines), organised around four principles: content should be Perceivable, Operable, Understandable, and Robust, with levels A, AA, and AAA. Most businesses aim for AA, which is also the bar most accessibility laws (like the ADA and the European Accessibility Act) are measured against.

Why accessibility is a business issue, not just a legal one

It's easy to file accessibility under "compliance" and forget it. But the reasons to care are commercial long before they're legal, here's what an inaccessible site actually costs you:

• Lost customers. People who can't use your site don't complain, they buy from someone whose site works. That's revenue leaving silently.
• Legal risk. Accessibility lawsuits and enforcement (ADA, the European Accessibility Act) are rising fast; an inaccessible site is a growing liability.
• SEO overlap. Much of what helps screen readers, alt text, semantic structure, clear labels, also helps search engines understand your site.
• Better UX for everyone. Captions help people in noisy places; high contrast helps in bright sun; keyboard support helps power users. Accessible is just better built.
• Brand and reach. An inclusive site signals a business that takes its customers seriously, and widens the audience you can serve.

Where accessibility actually breaks (and what to fix first)

You don't need to boil the ocean. A handful of issues cause most real-world barriers, fix these and you've solved the majority of the problem. Here's where the effort belongs versus where teams over-index:

How to make your site accessible, practically

Accessibility isn't a mysterious specialism; it's mostly disciplined fundamentals applied consistently. The sequence that actually works:

• Start with an honest audit. Run an automated checker to catch the obvious wins, then test by hand, because tools only catch part of it.
• Test with a keyboard. Unplug the mouse and try to use your site, tab through everything, act on every control. If you get stuck, so does a keyboard user.
• Fix contrast and text. Ensure text meets AA contrast, is resizable, and never relies on colour alone to convey meaning.
• Add the semantics. Real headings in order, alt text that describes the image's purpose, labels tied to inputs, and meaningful link text (not "click here").
• Make focus visible. Keyboard users need to see where they are, never remove focus outlines without replacing them with something clear.
• Test with real assistive tech. Try a screen reader on your key flows. Nothing surfaces problems like actually hearing your site read aloud.

The part nobody mentions: retrofitting is the expensive way

Accessibility is dramatically cheaper when it's built in from the start rather than bolted on after launch. Retrofitting an inaccessible site means unpicking decisions baked deep into the markup and design:

• Design for it early , contrast, focus states, and structure are almost free at design time, and costly to patch later.
• Bake it into components , get your buttons, forms, and modals right once and every page inherits it.
• Make it part of "done" , a quick keyboard and contrast check before shipping stops regressions piling up.
• Keep checking , accessibility drifts as new content and features get added, so it's a habit, not a one-off certificate.

So, how accessible is your site?

Run the two-minute test. Unplug your mouse and try to complete your most important action, buy, book, or enquire, using only the keyboard. Can you see where you are as you tab? Can you finish? Then look at your text on a bright screen: is it easy to read, or thin and low-contrast? If any of that made you wince, you're likely turning away customers and taking on avoidable risk.

You don't need to fix everything overnight, start with contrast, keyboard access, alt text, and labels, and build the rest into how you work. If you're not sure where you stand, an honest audit is the most useful first step, and usually cheaper to act on than most teams expect.

Step by step

Frequently asked questions