What "accessible" means, and why it's good business

"Accessible" is one of those words that sounds like a technical checkbox — something a developer ticks off near the end of a project. It's worth a clearer look, because an accessible website is simply a site that more people can actually use, and "more people can use it" isn't a technical concern. It's the whole point of having one.

What it actually means

An accessible website is one that works for people who aren't using it the way you might picture. Someone navigating by keyboard because they can't use a mouse. Someone using a screen reader that speaks the page aloud because they can't see it. Someone with low vision who needs larger text, or enough contrast to make out a button. Someone on a phone in bright sunlight, or with a temporary injury, or simply getting older — which is all of us, eventually.

Accessibility is the practice of building so that none of these people hit a wall. A form that can be completed without a mouse. Images described so a screen reader can convey them. Text that stays readable when enlarged. Buttons that announce what they do. None of it is exotic. Most of it is invisible to someone who doesn't need it, and essential to someone who does.

Why it's more than a courtesy

There are three reasons to care, beyond the plain one that shutting people out is worth avoiding.

The first is reach. The share of people who benefit from accessible design is far larger than most assume — not a rounding error, but a meaningful part of any audience, and a growing one as populations age. A site that excludes them excludes customers.

The second is that accessible sites are better sites for everyone. The same qualities that help a screen reader — sensible structure, clear labels, good contrast, text that doesn't fight the reader — make a page easier for anyone to use, including the visitor with perfect eyesight skimming on their phone. Accessibility and plain good usability are mostly the same thing wearing different names.

The third is that it increasingly carries legal weight. In many places, businesses have a duty not to exclude people with disabilities from services offered to the public, and websites have been treated as falling under that duty. The specifics vary and change, and this isn't legal advice — but "we never thought about it" is a weak place to be found standing.

How to tell if a site takes it seriously

You don't need to audit anyone's code. A couple of plain checks reveal a lot. Try moving through a site using only the Tab key — can you reach everything, and can you always see where you are? Enlarge the text in your browser — does the page still work, or does it fall apart? These are rough tests, but a site that fails them plainly wasn't built with much thought for anyone beyond a sharp-eyed visitor with a mouse and a big screen.

A firm that treats accessibility as fundamental builds it in from the start rather than adding it at the end — because retrofitting it later is harder, costlier, and never quite as good. It's the kind of thing that's cheap to do well when it's a habit and painful to bolt on when it isn't. Which tells you something useful about anyone who does it as a matter of course.