The Business Case for Accessibility Your CFO Will Understand

Most arguments for web accessibility are framed in ways that guarantee they lose budget fights. The moral framing, that excluding people is wrong, is true but converts poorly in a quarterly planning meeting, because it competes against projects with revenue numbers attached. The compliance framing, that the law may require it, converts a little better but positions accessibility as a cost to be minimized, which means it gets minimized. If you want accessibility work to actually get funded, you have to make the argument the way every other funded project makes it: in terms of markets, conversion, risk, and cost curves. The good news is that the honest version of that argument is strong.

Start with market reach, because it’s the frame a CFO already uses. Every business decision about geography, languages, and payment methods is a decision about which customers you’re able to serve. Accessibility is the same decision wearing different clothes. A significant fraction of the population has some disability affecting how they use the web, whether of vision, hearing, motor control, or cognition, and that fraction grows with age, which means it overlaps heavily with the demographic that holds the most disposable wealth. A site that can’t be used with a screen reader or navigated by keyboard has, in effect, geo-blocked a customer segment. No one would casually accept “our site doesn’t work in an entire region” as a permanent condition. This is that, minus the map.

The second frame is conversion, and here’s the part of the argument that’s underrated: accessibility work and conversion work are largely the same work. Consider what the actual fixes are. Sufficient contrast between text and background, so people with low vision can read your page, also makes it readable on a phone in sunlight. Descriptive link and button text, “Download the pricing PDF” instead of “click here,” helps screen reader users who navigate by jumping between links, and also helps every skimming visitor. Labels attached to form fields help blind users know what to type, and also keep the label visible for everyone after they’ve started typing, which reduces abandoned forms. Captions serve deaf users and the much larger population watching in open-plan offices with the sound off. There’s a name for design that works under constraint: robust. The overlap between “usable by people with disabilities” and “usable by everyone on their worst day” is so large that a CFO can treat accessibility spend as conversion spend with an extra market attached.

The third frame is risk, and it deserves exactly one paragraph, because it’s real but shouldn’t lead. In many jurisdictions, legal and regulatory pressure on inaccessible sites and apps is a live and growing exposure, and defending or settling a claim costs more than the fixes would have, without producing any product improvement. A CFO understands unhedged exposure. State it, size it for your jurisdiction with actual counsel rather than blog posts, and move on. If risk is your whole case, you’ll get the minimum, and the minimum is a bad product.

The fourth frame is the cost curve, and this is the argument I’d lead with, because it’s about timing, which is what budget decisions actually control. Accessibility has radically different costs depending on when you pay for it. Built in from the start, it’s nearly free: choosing an accessible color pair costs the same as choosing an inaccessible one, and writing the HTML correctly, real buttons instead of clickable divs, labels wired to inputs, headings in order, costs nothing but knowing to do it. Retrofitted across an established site, the same properties cost real engineering time, because they’re now entangled with everything built on top. The financial translation is that accessibility behaves like technical debt, with the same compounding interest. The question for the CFO isn’t “should we spend on accessibility,” it’s “at which point on the cost curve would we like to buy this,” and the answer to that framing is always the same: the earliest point still available, and a process that keeps you from sliding down the curve again.

That last clause matters, because accessibility isn’t a one-time purchase. Sites change weekly, and every change can quietly reintroduce a barrier, an unlabeled button in a new feature, a low-contrast banner from a seasonal redesign. The affordable version of accessibility is continuous and boring: catch regressions when they’re one line, not when they’re an initiative. That’s why accessibility is one of the six areas GazeSite audits on every scan, with each finding paired to a concrete remedy. The point is to keep the work in the cheap region of the curve permanently, which is a maintenance contract, a shape of spending any CFO recognizes and can price.

So the pitch, condensed to something that survives a meeting: there’s a customer segment we currently can’t serve, skewed older and wealthier. The work required to serve them measurably improves the product for everyone else, so it’s conversion spend, not charity. It hedges a legal exposure as a side effect. And it’s dramatically cheaper bought continuously than retrofitted later, so the only bad decision is deferral. Notice that nothing in that paragraph appeals to virtue. It doesn’t need to. The virtue comes free with the returns, which is the happiest kind of business case there is.