Fix Accessibility In-House or Hire a Specialist?

Opening answer

Fix accessibility in-house when your team already writes and ships code each week, and hire a specialist when the site is large, custom built, or under a tight deadline. A third route fits many small teams: a code fix service that finds issues, fixes code where it can, and leaves a dated record of the work. The right choice turns on three facts: how many people can do the work, how much time and money you can give it, and how soon the fixes must be live.

The three routes in plain terms

In-house work means your own developers and content editors find issues and change the code. A specialist means an outside expert audits the site, writes a fix plan, and in many cases fixes the code or guides your team through the fixes. A code fix service sits between those two routes. It scans the site, fixes set categories in code, and hands back a dated record.

None of these routes, on its own, proves a site meets every WCAG criterion. Automated checks catch only part of the picture, and ADA.gov guidance says a clean report does not necessarily mean everything is accessible. Pair any automated step with a human check of keyboard use, forms, captions and reading order.

Fix it in-house when the team fits the work

In-house work fits when developers can own the job for several weeks, and when content editors can fix alt text, headings and link text as part of normal publishing. It also fits when the site is small, built on a standard theme, and changed slowly. The team can then fix issues page by page, test each fix, and keep a dated list of what changed.

The cost here is staff time, not a vendor fee, and the gain is skill that stays in the team. The risk is drift: new pages and templates can bring back the same issues, so the team needs a repeat check. In-house work fits less well when no one has fixed accessibility issues before, or when the only developer also runs sales, support and hosting.

Hire a specialist when the stakes or the scale demand it

Hire a specialist when the site is large, when it has custom code that a scan cannot judge, or when a deadline is set by a client or a funder. A specialist can audit against WCAG 2.2 AA, sort findings by impact, test with a keyboard and a screen reader, and write fixes your developers can apply.

Ask any specialist for three items before you agree a fee: the scope of pages and templates, the form the fixes will take, and the record you will hold at the end. A report alone, with no code changes and no retest, leaves the hardest part still to do. A specialist is a poor fit when the budget covers only an audit, with nothing left for fixes or a retest.

Decision list by team size, budget and speed

Use this list in order. Stop at the first route that fits your facts.

• Solo owner, no developer, small site, low budget, no deadline: start with a free scan and a code fix service, then fix content issues from the checklist.
• Solo owner, no developer, small site, low budget, fast deadline: use a code fix service for code issues, and hire a specialist only for a short review of forms and checkout.
• Small team, one developer, medium site, modest budget, steady pace: fix in-house with a scan and a checklist, and book a specialist review at the end of the first pass.
• Small team, one developer, medium site, modest budget, fast deadline: hire a specialist for the audit and fix order, and let your developer apply the fixes in that order.
• Agency with several client sites, steady budget: use a code fix service across sites for repeat code issues, and hire a specialist for custom code or fixed deadlines.
• Large or custom site, many templates, large PDF or video set, fixed deadline: hire a specialist first, and keep a code fix service or an in-house owner for monitoring after.
• Any team, after a demand letter or a lawsuit: talk to a qualified attorney first, then use a scan and a specialist to build a dated record of fixes.

This is general information, not legal advice. If you have received a demand letter or been sued, talk to a qualified attorney.

What Axeazy adds for a small team

Axeazy fits a reader who wants code level fixes without hiring a full time specialist. It scans with axe-core, fixes 14 categories at code level, and keeps a dated record of scans and fixes. For a site with a GitHub repo, fixes arrive as a real pull request with a visible diff for owner review.

For WordPress, a free plugin applies exactly three instant fixes at render time: a skip navigation link, a page language attribute, and an alt text fallback, with no account needed. For Shopify, Axeazy scans the store and gives a guided plain English checklist, and it does not open pull requests against Shopify theme templates. For other sites, Axeazy gives computed fix values plus a guided checklist, with no automatic changes.

Colour contrast is detected and a WCAG correct colour is calculated, but it is never applied without owner approval. Paid plans give PDF reports and weekly monitoring. Run Axeazy's free scan to see the scale of issues on your own site, then compare Axeazy's pricing page for the plan that fits your site count.

The capabilities page lists Starter at $29 a month, Pro at $79 a month and Agency at $199 a month, with paid prices shown at checkout on the pricing page and annual billing saving 20 to 25 percent. Use those figures only with that checkout caveat. For a fuller price and fit comparison, see: Axeazy vs accessiBe: Price, Fixes and Fit.

How to choose, and common mistakes

First, name the job in one sentence. Second, count pages and templates, not just the home page. Third, ask who will test each fix, who will merge it, and who will hold the dated record. Fourth, try the free step before you pay, and use the result to scope the paid work.

Common mistakes waste the first month: buying a scan and stopping there, with no owner for fixes; hiring a specialist for an audit, then leaving no budget for fixes or a retest; and fixing only the home page, while forms and checkout keep the same issues.

Adding a visitor menu and treating it as a code fix, when the source code stays unchanged, is another mistake. So is losing the record: fixes with no date, no page list and no retest are hard to show to a client or an attorney later. Write down the scope, the owner, the fix order and the retest date before work starts. That short plan can reduce risk over time.

FAQ

Should I fix accessibility in-house or hire a specialist?

Fix in-house when your team writes code each week, the site is small, and you can name an owner for testing and retests. Hire a specialist when the site is large or custom built, when forms and checkout need human testing, or when a deadline leaves no room for learning on the job.

How do I choose if my budget is small?

Start with the free scan and the free WordPress plugin where they fit, then fix content issues from the checklist. Spend paid money first on the pages visitors use most, such as forms, checkout and contact pages.

What should I ask a specialist before hiring one?

Ask for the scope of pages and templates, the form fixes will take, and whether a retest is included. Ask how findings will be sorted by impact, and what record you will hold at the end.

Does a code fix service replace a specialist?

No. A code fix service helps you find and fix set categories in code, and it gives a dated record of that work. A specialist adds human testing of keyboard use, forms, reading order, captions and custom flows that automated checks cannot judge.

What do I do first if I got a demand letter?

Talk to a qualified attorney before you change the site in a rush, and keep every letter and date in one file. A scan can then give you real data about what is wrong and what has already been fixed.

Last checked and sources

Last checked: October 31, 2026.

Sources: ADA.gov guidance on web accessibility and the ADA, WCAG 2.2.

If you want code fixes and a dated record to start from, read the honest scope on Axeazy's capabilities page before you choose a plan.

Related reading

• Best Accessibility Tools for Small Business