Accessibility usually gets pitched to a business owner in one of two ways: as a legal-compliance checkbox, or as a goodwill gesture toward a small number of visitors. Both framings undersell it, and both make it easy to deprioritise, because a checkbox feels like a cost with no upside and a goodwill gesture feels optional. Neither framing accounts for the size of the audience actually affected, or for how cheap the highest-impact fixes usually are compared to everything else competing for a web budget.
The audience is larger and less visible than assumed
Permanent disabilities are only part of the picture. A far larger group experiences accessibility barriers situationally or temporarily — someone browsing in bright sunlight who needs sufficient colour contrast to read anything at all, someone with a temporary arm injury navigating by keyboard instead of a mouse, someone on a slow connection who never sees images that carry no text alternative, someone reading in a second language who benefits from clear structure and plain wording as much as any screen-reader user does. None of this shows up in a typical set of analytics as "accessibility problem" — it shows up as an unexplained exit, indistinguishable from any other visitor who simply left, which is exactly why it goes unaddressed for years.
Where the return is highest relative to the cost
Sufficient colour contrast between text and its background is close to free to fix and helps every visitor in poor lighting or with any degree of low vision, not a narrow group. Writing a real, specific description for every meaningful image — not the filename, not a blank tag — takes a few minutes per image and immediately makes that content available to a screen-reader user and to search engines simultaneously. Making every interactive element reachable and usable by keyboard alone, without a mouse, is largely a matter of not actively breaking the browser's own default behaviour, which already supports this — most of the cost here is accidentally introduced by custom components that override defaults without rebuilding what they removed. Clear heading structure and plain, direct language help a screen-reader user navigate the page in seconds instead of minutes, and simultaneously help every visitor scan the page faster, because scannable structure is not a separate feature for one audience — it is the same thing good writing already does.
What doesn't need doing first
A full technical audit against every clause of an accessibility standard is a real project with real value, but it is not where to start, and treating it as the entry price often means nothing gets fixed at all while the audit is pending. The handful of fixes above cover a large share of real-world barriers on their own, cost little, and can be done this month rather than scheduled for a future budget cycle.
The commercial argument, stated plainly
An inaccessible site doesn't just exclude visitors on ethical grounds — it exclude a segment of demand that a competitor's more accessible page will simply pick up instead, at no extra spend on ads or reach. Contrast, alt text, keyboard access and plain structure are inexpensive precisely because they were never separate accessibility features bolted onto a design — they are the same properties that make a page work better for everyone, once a team stops treating "accessible" and "well-built" as two different projects.
This sits alongside the other quiet leaks covered in treating the website as a working business system — the visitors a site loses without a complaint ever being filed. Our web team can flag the highest-return fixes on a specific site without requiring a full audit as the starting point.
