The in-house illusion: why hiring an accessibility lead isn't a compliance strategy
A Forbes Tech Council post this week put a number on something the industry has been quietly avoiding. Accessibility settlements typically run $25,000 to $100,000 per case, before legal fees, executive time, and the remediation work that has to happen anyway as part of any settlement.
That's the bill. The interesting question is who keeps writing the cheque.
It's almost never the company without an accessibility programme. It's the company that has one.
The reassuring hire
The pattern goes like this. Legal flags exposure. A board member reads an article. Someone forwards a link about the European Accessibility Act. The response is to hire an accessibility lead, or appoint a champion from the existing team, or stand up a working group.
The role gets a title. The title gets a slide in the all-hands. The slide reassures everyone that accessibility is being managed.
This is the in-house illusion. The work of managing accessibility, the meetings, the audits, the quarterly reports, starts to feel indistinguishable from the work of being accessible. They are not the same thing. One produces calendar invites. The other produces compliant software.
One person, every pull request
Pick any reasonably active codebase. Count the pull requests merged last month. Now imagine one person manually reviewing each one for keyboard traps, focus order, contrast ratios, ARIA misuse, heading hierarchy, form labelling, reflow behaviour, motion sensitivity, and the forty other things WCAG 2.2 actually asks for.
They can't. Nobody can. The work scales with the codebase, not with headcount.
So the accessibility lead does what any reasonable person would do. They prioritise. They focus on the highest-risk surfaces. They run quarterly audits. They write a style guide. They train the team. They do all the things a single human can do, and the codebase keeps shipping, and most of what ships never gets reviewed by them at all.
Then a settlement letter arrives, and the question from the board is: "But we hired someone for this. What happened?"
What happened is that hiring a person was never going to be enough. The work needed a system.
Where the lawsuits actually live
The gap between "we have an accessibility programme" and "every merge is compliant" is where the $25k to $100k cheques get written. We've written before about the enforcement gap, the space between an AI finding issues and being able to prove they were fixed. The in-house illusion is the same gap, dressed up in headcount.
A team with an accessibility lead and no enforcement pipeline is in the exact same legal position as a team with neither. The audit log doesn't say "but we tried." The plaintiff's lawyer doesn't care that there was a champion. The regulator wants to know which components were checked, when, against what criterion, and whether the fixes were verified. If the answer lives in the head of one person who reviewed twelve PRs out of three hundred, there is no answer.
This is the part the Forbes piece gets right and most internal accessibility programmes get wrong. Settlements aren't priced on intent. They're priced on outcomes that can be evidenced, or the absence of them.
What a pipeline looks like
The companies not getting sued aren't the ones with the biggest accessibility teams. They're the ones who moved the work out of a single role and into the build itself.
That looks like rules running on every pull request, not in a quarterly audit. It looks like findings going into a tracked system the moment they're detected, not into a chat transcript that disappears at the end of the session. It looks like fixes being verified against criteria before they merge, not waved through because someone said they were done. And it looks like an audit trail that exists by default, because every step of the cycle wrote to it automatically.
The accessibility lead, in this version, isn't the bottleneck. They're the person who designs the pipeline, decides what the rules should be, handles the 40% of issues that genuinely need human judgement, and presents the evidence when someone asks for it. They're a force multiplier instead of a single point of failure.
The difference matters because one of these scales with the company and one of them doesn't.
The compliance framing
The other thing the Forbes piece does, almost incidentally, is reframe the conversation away from accessibility-as-virtue and towards accessibility-as-risk-management. This is the framing executives actually respond to. We've heard the same thing from technical leaders we've spoken to: nobody opens a budget meeting saying "make us more accessible." They open it saying "make us compliant with the law."
That's not cynicism. It's how compliance gets funded. And it's why the in-house illusion is so dangerous. A virtue framing tolerates "we're trying our best." A risk framing doesn't, because the cheque amount is the same whether you tried or not.
Compliance isn't a role. It's a pipeline. The role is what designs and runs the pipeline, but the pipeline is what produces the evidence that keeps the settlement letters in the drawer.
Try it
Look at your last twenty merged pull requests. For each one, ask: who reviewed it for accessibility, against which criteria, and where is that record stored?
If the answer is "our accessibility lead, when they have time, and it's in their head," the illusion is in the room.
Jeikin is what we built to close that gap. Every PR gets the same review. Every finding gets tracked. Every fix gets verified. The accessibility lead stops being the bottleneck and starts being the person who proves it works.
Hiring someone to care about accessibility is a good first step. Treating that hire as the strategy is where the cheques start getting written.