When teams go looking for an accessibility audit, a lot of them assume they need an agency. Big company, big compliance problem, must need a big supplier. In my experience that assumption costs people money without buying them better work.
I’m freelance, so again, I have a perspective here. But let me try to give you the honest version.
What agencies actually provide
There are a handful of genuinely excellent accessibility consultancies. They have teams, bench depth, and can run large engagements across multiple workstreams simultaneously. If you’re a bank rolling out a new platform across twelve countries and you need a team of eight auditors working in parallel, go find one of those.
Most teams aren’t in that situation. Most teams have a website, or an app, or a SaaS product, and they need someone to tell them what’s wrong and help them fix it. For that work, the agency overhead, account management, project management, margin on junior staff time. It doesn’t add value. It just adds cost and introduces a layer between you and the person doing the actual work.
The other thing agencies sometimes do is put senior names on proposals, deliver junior time. The person who impressed you in the pitch isn’t necessarily the person running your audit. It’s worth asking directly who will do the work.
What freelancers actually provide
When you hire a freelance accessibility auditor, you know who you’re getting. The person you speak to in the scoping call is the person who tests your product and writes your report. That’s useful, and not just for accountability, it means the findings are written by someone who understands the full context of what they found.
Good freelancer tend to have depth rather than breadth. They’ve tested a lot of products over a long time, they know the common failure patterns, and they know where the genuinely tricky interpretation questions live. That depth is what you’re buying.
The trade-off is capacity. A freelancer can’t run ten simultaneous engagements. If your timeline is very tight and your scope is very large, that might be a constraint. Most of the time it isn’t.
However a freelancer is also able to hire, need a product manager, sure - we can get that sorted.
What makes a good freelance accessibility developer
The same things that make any good WCAG specialist good, but worth repeating in this context.
They test manually. Automated tools are part of the workflow, not the whole workflow. Keyboard navigation, screen reader testing (NVDA and JAWS on Windows, VoiceOver on Mac and iOS at minimum), zoom testing these are non-negotiable parts. If someone’s process doesn’t include them, the work isn’t thorough.
They write findings that are actually usable.
I’ve taken over audits from other people before, and occasionally the report is so underspecified that the development team has no idea what to do with it.
Every finding should tell you what the problem is, where it is, which WCAG criterion it maps to, why it matters to a real person using the site, and what a fix looks like. That’s what a developer needs to act on it. Sometimes what are the Design solutions.
They’re honest about grey areas. Some accessibility questions don’t have clean answers. The spec is genuinely ambiguous on certain points. A good auditor tells you when something is contested, gives you their view and their reasoning, and lets you make an informed decision. Someone who presents everything as black-and-white probably hasn’t thought about it hard enough.
On platforms vs direct
Hiring through a work marketplace like Upwork or Fiverr is fine as a starting point. The rankings are driven by activity, reviews, and keyword density, none of which directly measure accessibility expertise.
The best hires I know of in this space come from referrals within the accessibility community, or from finding someone whose public writing demonstrates real knowledge. If someone has written substantively about WCAG.
A practical note on retesting
One thing that often gets under budgeted, retesting after fixes. An audit tells you what’s broken. Retesting confirms it’s been fixed correctly and that the fix didn’t introduce new issues. Factor that into your engagement.
I work as a freelance accessibility developer, mostly with product teams and organisations that need to get their WCAG issues fixed. If you want to understand what an engagement would look like, my work page has more.