The Accessibility Pricing Gap

A couple of weeks ago I got on a call with the head of engineering at a company with a few dozen people. Not a giant, but not a startup either. A real product, real customers, a website that had quietly grown into something complicated. He’d gotten a legal demand letter about accessibility a few weeks earlier, he wanted to do the right thing, and he was stuck. He’d spent an afternoon shopping for tools, hit a wall, and gone looking for someone who could tell him what he was missing. That’s how we ended up talking.

What he’d run into is what I call the accessibility pricing gap. He had three kinds of tools to choose from, and not one of them was built for a team like his or the job ahead of them. Free scanners that point out what’s broken and then leave you to fix it alone. Overlay widgets that promise to make your site compliant automatically, which is a promise no line of JavaScript can keep. And enterprise platforms that quote you a five-figure annual contract and assign you a sales rep before they’ll show you a price. Too shallow, too dishonest, or too expensive. Most people in his position give up right there. They close the tabs, go back to work, and the demand letter goes in a drawer. He didn’t, which is honestly the only reason we were on the call.

That’s the part that bothers me. He had the budget to pay for the right tool and every intention of using it. The market just hadn’t built a door for him to walk through, and the only reason he found one is that he got stubborn enough to keep looking. Most people aren’t, and I don’t blame them.

Three tiers, and a trap where the middle should be

If you’ve shopped for accessibility tooling, you’ve met all three of these.

Free scanners. Usually a browser add-on you install and run on a page. It flags what’s broken: color contrast failures, missing alt text, unlabeled form fields. That’s genuinely useful for a first pass. But it stops right where the hard part starts. It won’t walk you through a fix, it won’t track your progress over time, and it won’t generate the reports you need to show a client, a boss, or a lawyer. It tells you something is wrong and then hands you the responsibility for figuring out the rest.

Free scanners tell you something is wrong, then hand you the responsibility for figuring out the rest.

Overlay widgets. A step up in price, and the most dangerous option on the list. These are the tools that promise to make your site compliant automatically with a single line of JavaScript. They can’t. Accessibility isn’t a layer you bolt on at runtime, and a script can’t understand your content, your context, or what your users actually need. What they hand you instead is a badge and a false sense of safety, while real users still can’t use your site and the site running the widget can become a target in an accessibility lawsuit of its own. They’re affordable, they’re easy to install, and they solve the wrong problem convincingly enough to fool a lot of well-meaning people.

Enterprise platforms. These do the real work: deep scanning, fix guidance, monitoring, reporting, the whole picture. They also cost more than most teams spend on their entire development tooling budget for the year, and they’re sold through demos and procurement cycles and annual commitments. That model exists for a reason. Large organizations have the budget, the dedicated accessibility staff, and the compliance pressure to justify it.

So look at what’s actually on offer to a mid-market team. The honest tools are either too shallow to help or too expensive to reach. And the one option priced for a normal budget is the one that doesn’t work. That’s the gap.

Who actually lives in the mid-market

When I say mid-market, I’m not talking about one kind of company. I’m talking about the agency with eight developers building sites for a dozen clients. The growing software company that just hired its first designer and doesn’t have anyone who owns accessibility. The small, rural county government or a community college that has real legal obligations and a budget that would make an enterprise sales rep laugh. The in-house team of three who got handed accessibility on top of everything else they already do.

These teams have something in common. They’re past the point where “we’ll deal with it later” is safe. They have enough traffic, enough customers, and enough exposure that accessibility is a real risk and a real responsibility. But they don’t have a six-figure compliance budget or a person whose entire job is accessibility.

They’re the most common kind of team building and maintaining stuff on the web. And they’re the ones the tooling market has decided not to serve.

Why the gap exists

Most of this isn’t a story about villains. The honest tools land where they land because of how software gets sold, not because anyone set out to exclude these teams.

The one price point a mid-market team can actually afford got colonized by the worst option on the market.

Enterprise platforms are built around an enterprise sales motion. High-touch demos, custom contracts, long procurement cycles. That motion is expensive to run, so it only pays off when the deals are big, which means the whole product gets shaped around customers who can write big checks. Self-serve pricing, a free starting point, plain-language guidance a non-specialist can follow on their own, those things don’t fit the model, so they don’t get built.

Free scanners have the opposite problem. They’re often a loss leader or an open-source side project, so there’s no business reason to build the expensive, hard parts: the fix guidance, the monitoring, the reporting, the workflow that turns a list of problems into actual repaired pages. The depth costs money to build, and free tools don’t have a model that funds it.

And then there are the overlays, which exist for an uglier reason. There’s real demand for a quick fix, and it turns out you can make good money selling one that doesn’t work. They filled the affordable middle not by solving the problem but by convincingly pretending to. So the one price point a mid-market team can actually afford got colonized by the worst option on the market.

So the middle falls through. Not because mid-market teams don’t want to pay. Because the honest tools were never priced for them, and the one that was is a trap.

What getting left behind actually costs

When a team can’t find a tool that fits, the cost isn’t just inconvenience. It’s that accessibility doesn’t happen.

I’ve written before about the find-to-fix gap, the fact that our industry got very good at finding accessibility problems and never solved the part where someone who isn’t an accessibility expert actually fixes them. The pricing gap stacks right on top of that. Even when an affordable tool can find your issues, the affordable tier usually can’t help you fix them, and the tier that can help is out of reach. So the issues get found and then they sit there.

Meanwhile the people who can’t use the site are still locked out. The legal exposure is still there. And the team that genuinely wanted to do better walks away feeling like accessibility is something only big companies with big budgets get to do well.

That’s a lie, and it’s an expensive one. It teaches a whole tier of the market that accessibility isn’t for them.

The tools themselves should be accessible, including the price

There’s an irony I think about a lot. We talk constantly about making the web accessible, about removing barriers so everyone can participate. And then we build the tools to do that work behind a barrier of our own: a price and a sales process that shuts out most of the people who’d use them.

If we actually believe accessibility is for everyone, the tools have to be reachable by everyone who has the job of building it. That means a real free starting point, not a teaser. It means pricing you can see and understand without a sales call. It means guidance written for the developer who was never taught any of this, because that’s most developers. Accessibility of the tooling isn’t a nice-to-have. It’s the same principle we’re asking everyone else to live by.

I’ve watched just how strange transparent pricing has become in this space. I’ll be on a sales call and ask, “Did you have any questions after looking over the pricing on our website?” More than once, the person has been genuinely surprised the pricing was there at all. It hadn’t occurred to them to even look, because every other tool they’d evaluated made them book a call to find out. We’ve trained a whole market to expect that a price is something you extract from a salesperson instead of something a company will just tell you.

Built for the teams in the middle

This is the gap we built AAArdvark to close. You can start free, on your real homepage, and see exactly where you stand without talking to anyone. When you’re ready for more, you can see exactly what every plan costs on our pricing page, no sales call required. And every issue comes with plain-language guidance on what’s wrong, why it matters, and how to fix it, because finding problems was never the hard part and pretending to fix them was never an option.

I built it for the head of engineering on that call. For the eight-person agency, the three-person in-house team, the county government with real obligations and a normal budget. The teams who wanted to do the right thing and just needed a door built for them.

If that’s you, you’re not too small to take accessibility seriously. The market just hadn’t gotten around to you yet.