Accessibility and Conversion: The Overlap Founders Miss

There’s a strange accounting error I keep seeing in startups. Accessibility gets filed under compliance, a cost, something you do reluctantly when a lawyer or a big customer forces the issue. Conversion optimization gets filed under growth, an investment, something you do eagerly because it makes money. And yet when you look at the actual work, at the actual changes to the actual pages, the two lists overlap so much that keeping separate ledgers is almost comical.

Consider what a conversion consultant tells you. Make the button text say what happens when you click it. Make the form labels clear. Make error messages tell people what went wrong and how to fix it. Increase contrast so the call to action stands out. Don’t rely on color alone to convey meaning, because it’s ambiguous. Make the page usable on a phone held in one hand. Cut anything that moves or blinks and distracts from the goal.

Now consider what an accessibility audit tells you. Buttons must have accessible names that describe their action. Form inputs must have programmatically associated labels. Errors must be identified in text and suggest corrections. Text must meet minimum contrast ratios. Information must not be conveyed by color alone. Touch targets must be large enough to hit. Motion should be reducible or avoidable.

These are the same lists. One is phrased in the language of persuasion and one in the language of standards, but they describe the same underlying reality: a page that is easy to perceive, easy to understand, and easy to operate. WCAG, the accessibility standard everyone cites and few read, organizes itself around exactly those words. Perceivable, operable, understandable. It could be the table of contents of a conversion book.

The reason for the overlap isn’t a coincidence. It’s that both disciplines are fighting the same enemy: friction. A user with low vision who can’t read your gray-on-white body text and a user in bright sunlight who can’t read your gray-on-white body text hit the same wall. The first user is counted in accessibility statistics and the second in bounce rate, but your revenue can’t tell them apart. A checkout form whose fields have no labels defeats a screen reader completely and defeats everyone else partially, because placeholder text vanishes the moment you start typing and now you’re guessing whether that field wanted your card number or your phone.

I built GazeSite partly because I got tired of seeing these two conversations happen in different rooms. When we grade a site, accessibility and conversion are separate focus areas, and it’s remarkable how often a finding in one is a paraphrase of a finding in the other. A missing label shows up as an accessibility failure and, two sections later, as a checkout-friction warning. Same element, same fix, two reasons to make it.

Founders miss the overlap because of who delivers the message. Accessibility arrives as an obligation, usually late, usually framed as risk. Nobody gets excited about risk. Conversion arrives as opportunity, framed in dollars. But if you re-derive accessibility from first principles instead of from fear, you get something like this: some fraction of the people who want to give you money cannot currently operate your website. For most sites that fraction is not small, because it includes not just people with permanent disabilities but everyone temporarily impaired, tired, distracted, on a cracked screen, on a train. Making the site operable for the people who have it hardest makes it smoother for everyone else, the same way curb cuts built for wheelchairs turned out to be great for strollers and suitcases.

There’s a practical consequence to seeing it this way. If accessibility and conversion are mostly the same work, you should stop scheduling them separately. The quarter you spend redesigning the checkout is the quarter to fix its labels, its focus order, its error handling, because the marginal cost of doing it then is nearly zero and the marginal cost of a retrofit later is a rewrite. Accessibility done as a project is expensive. Accessibility done as a habit, inside the work you were already doing for conversion reasons, is close to free.

The founders who get this tend to be the ones who have watched a real user struggle. It’s one thing to see “insufficient contrast” in a report and another to watch someone lean toward the screen, squint, and give up. The report says compliance. The squint says lost sale. They were always the same thing. The overlap was never missing from the product. It was only missing from the org chart.