Website accessibility matters: practical work, not a slogan

Accessibility is not a compliance slogan: it is the difference between a site that works for everyone and a site that works for you.

Ask around and you will hear accessibility described as a compliance slogan, something large companies hire consultants to certify after the site is already built. We think that framing misses who is actually on the other side of the screen. Among the people trying to reach your business are customers who navigate entire sites with a screen reader, and customers whose eyes are tired or whose hands never touch a mouse. They are not an edge case. They are part of your market, and no analytics dashboard tells you how many of them you already lost.

The practical work is unglamorous and it overlaps almost completely with good engineering. Give every image a meaningful text alternative and the site becomes readable by screen readers and by search crawlers, which are, in this one respect, the same kind of visitor. Build forms that work from a keyboard alone and you have also built forms that work on a phone with a stubborn screen. Keep contrast readable and headings in a real hierarchy, and the page becomes clearer for every reader, assisted or not. Serving assistive technology and serving everyone turn out to be the same work.

There is a market reason on top of the principled one. In this region a large share of buyers browse on older phones, on weaker networks, in bright sunlight, at the end of a long working day. The practices above are exactly what make a page light, fast, and forgiving under those conditions. A site a screen reader can walk through is usually a site that loads quickly on a phone a few years old. We see no tension between doing the right thing and doing the commercially smart thing. They are the same checklist.

The discipline that matters is timing. Accessibility built in at the start is a set of habits: alt text written as content is authored, and contrast decided when colors are chosen, and forms that can be completed from a keyboard alone from day one. Retrofitting the same things after launch, or worse after a complaint, means reopening finished pages and paying twice for one job. We build new pages with these habits in the first pass, because we would rather carry the habit than the debt.

Concretely, this is what it looks like on our own site: images carry descriptions that mean something, buttons and links are reachable and labeled from the keyboard alone, headings follow a structure a screen reader can walk without guessing, and both the dark and light themes keep text readable rather than merely fashionable. When we test a page, we do not stop at whether it looks right on a fast laptop. We ask whether it survives a small screen on a slow connection, and whether it still works for a reader who cannot see it at all.

We are not auditors and this essay is not a legal standard. Where formal requirements apply to your sector or your contracts, the specifics belong with specialists who read those rules for a living. What we will defend is the engineering claim: the accessible version of a page is almost always the better-built version. Building it early is cheaper than apologizing later, and the visitor your site helps least is a better test of it than the most powerful device you own.