A graphic featuring a map of Europe in dark blue with a lighter blue figure in a circle at the centre, symbolising accessibility. The circle is surrounded by a ring of twelve yellow stars, representing the European Union, against a deep blue background.

Most teams looking for accessibility help are choosing between an agency, a large consultancy, or a freelancer. Here’s when a freelance accessibility consultant in the UK makes more sense than the alternatives, and what to actually look for.

Why freelance over agency

The main reason teams hire a freelance accessibility specialist rather than an agency is that you’re working directly with the person doing the work. With an agency, you’re often buying the relationship with a senior consultant but receiving work from someone more junior. That’s not universal, but it’s common enough to be worth asking about.

Freelancers also tend to be more flexible. Scoping, scheduling, and communication tend to be simpler when there is one person rather than a layer of account management between you and the work.

Cost is a factor too. A freelancer doesn’t carry agency overheads, which typically means better value for equivalent quality of work.

When an agency or larger consultancy makes more sense

There are situations where scale matters. If you need a team of specialists working simultaneously across a large estate, a single freelancer can’t deliver that. If you need formal indemnity and legal cover built into a supplier contract, some procurement frameworks require that. Public sector contracts in particular sometimes require supplier tiers that rule out individual consultants.

But for the majority of projects, those constraints don’t apply.

What to look for in a freelance accessibility consultant

Real testing methodology. Automated tools (axe, WAVE, Lighthouse) are useful for catching obvious issues, but they only detect around 30 to 40% of real WCAG failures. Ask directly: do you do manual testing? Do you test with keyboard only? What screen readers do you use? The answer should name specific tools: NVDA on Windows, JAWS, VoiceOver on macOS and iOS at minimum.

Experience with your type of product. Accessibility in a complex web application is different from a content site. Accessibility in a banking interface is different from an eCommerce checkout. It’s worth asking if they have relevant experience with your product type.

Useful output. An accessibility audit is only as valuable as what the team does with it. Ask to see a sample report. Does it explain the real impact of each issue? Does it map findings to specific WCAG success criteria? Does it give developers enough to act on without a follow-up call? If the answer to any of those is no, the report won’t drive change.

Pragmatism. Accessibility work in real teams involves tradeoffs. A good consultant understands that remediation happens in stages, that some things are harder to fix than others, and that the goal is meaningful progress rather than perfection on paper.

What working with a freelancer typically involves

For a scoped audit, it usually starts with a brief conversation to clarify scope, followed by testing, and a written report with findings, impact descriptions, and fix guidance. Depending on the size of the project, turnaround is typically one to three weeks.

For ongoing or embedded work, it can look like regular design reviews, sprint support, or a block of time each month available for questions, reviews, and testing.

I’m a freelance accessibility consultant based in the UK. I work with digital teams across product, design, and engineering. If you want to talk through what you need, get in touch.