Website Accessibility Consultant: What They Do and When

A website accessibility consultant checks your site against WCAG, finds the barriers that block people with disability, and shows your team how to fix them. Part auditor, part coach, part evidence trail. They pair automated scans with real human testing, then hand you a ranked plan you can act on.

That last part, the plan you can act on, is what separates a consultant from a scanner. So let me walk through when you need one and how to pick a good one.

When do you actually need one?

You do not always need a consultant. Honestly, plenty of small sites can start with a free scan and a checklist. So here is the line I draw with clients.

Hire one when the stakes or the complexity climb. A few signals:

• You have had a complaint, a legal letter, or a government tender that asks for WCAG conformance.
• Your site runs custom components, a booking flow, or a single-page app that scanners misread.
• You need a dated evidence trail, not just a passing score.
• Nobody on your team has tested with a screen reader such as NVDA or VoiceOver.

If none of that is true, a tool plus an internal owner might carry you for a while. That is a fair place to start. The trouble is that tools miss most of what blocks people. The WebAIM Million, which scans a million home pages a year, found detectable failures on 95.9% of them in 2024, at 56.8 errors each. And those are only the ones a scanner can catch alone.

Automated tool vs in-house vs consultant

Here is the honest three-way split. Same site, three ways to check it.

Read that middle column carefully. In-house can work well, but only if someone owns it and knows the assistive tech. Most teams do not, through no fault of their own. So the practical choice is often a consultant for the deep pass, then in-house for the upkeep after.

Automated tools still earn their place. WAVE, axe and Google Lighthouse are quick and free, and they flag colour contrast or missing alt text in seconds. Use them. Just do not mistake a green score for a working site. A tool can tell you an image has no alt text. It cannot tell you the alt text reads “IMG_4471”.

How to choose one

This is where people get burned, so I will be specific. A one-click scan with a logo on top is not a consultant. Ask these before you sign anything:

• Do they test by hand with a screen reader, or only run a scanner?
• Will they report by template rather than by page, so you fix root causes?
• Do they map each finding to a WCAG 2.2 success criterion and a level?
• Is a retest after your fixes included in the price?
• Can they show real case work with numbers, instead of a stock badge?

A consultant worth hiring will answer all five without flinching. If the pitch is a dashboard and a monthly fee with no human testing, keep looking. You are paying for judgement, not a subscription. The benchmark itself is public: the Web Content Accessibility Guidelines, currently version 2.2, and the W3C evaluation guidance treats Level AA as the working target most organisations aim for.

What the engagement looks like

A good engagement is short and shaped. First a scope call, where we agree which templates and which WCAG level you are targeting, usually Level AA. Then the review, part automated and part manual, with a person driving a keyboard and a screen reader through your key flows. Then the report.

The deliverables are the point. You should walk away with:

• A ranked list of findings, each tied to a WCAG criterion and a severity.
• A fix note for every item, written for your developers.
• A retest once the fixes land, with a dated before-and-after on file.

That paper trail matters in Australia. The Australian Human Rights Commission points to WCAG as its benchmark, so a mapped, dated report is your evidence if a complaint arrives. The Disability Discrimination Act 1992 sets the underlying duty, and your website counts as a service. In the United States the same logic holds under the Americans with Disabilities Act, which is why the two jobs so often travel together.

What drives the cost

Straight answer: it depends, and a flat fee quoted before anyone sees your site is a guess. The number moves with a few things.

• Templates, not pages. A site of 200 pages built from 8 templates is 8 audits, not 200.
• The WCAG level you target. Level AA is the common bar, and Level AAA costs more.
• Whether screen-reader testing is included. It should be.
• Whether a retest is in the price, or billed later.

Avoid the open-ended hourly deal. Ask for a fixed scope with those four points named. If they are not written down, the number will drift, and the frustrating surprise lands on your next invoice. Take that with a grain of salt for very large or unusual sites. For most businesses it holds.

What we saw at AllHealth

I will show our workings, because “trust me” is not evidence. On a recent ADA compliance audit for a medical group, we worked page by page through a 37 page site. We found 213 WAVE errors. The average accessibility score sat at 4.1 out of 10, and not one page met Level AA.

The finding that stopped us was the appointment form. A keyboard user could reach it and then could not submit it. It looked fine to anyone using a mouse, which is exactly why a scanner and a busy in-house team had both missed it. That’s the gap a consultant is for. The relief, once we mapped and fixed it, was worth the week.

You can read the full write-up in our ADA compliance case study, and the service sits under ADA and AHRC compliance. If you want the mechanics of the review itself, we cover that in what a website accessibility audit is. For the sector specifics, there is ADA compliance for medical websites. This article is about the decision to hire. Those two cover the work.

One more honest note. A consultant is not a permanent fixture. The point of a good engagement is to leave your team able to prioritise and recognise the common barriers on their own, so the next scan you run means something. If a vendor tries to lock you into a forever subscription with no handover, that is a signal to walk.

FAQ

What does a website accessibility consultant do?

They check your site against WCAG, find the barriers that stop people with disability from using it, and show your developers how to fix each one. The useful ones mix automated scanning with real human testing, including a screen reader, then hand back a ranked plan. A bare score is not the job.

When should I hire one instead of using a tool?

Hire one when the stakes or the complexity rise. A legal letter, a tender asking for WCAG conformance, a custom booking flow that scanners misread, or no one in-house who has used a screen reader. If none of that fits, a free tool and an internal owner can hold you over for a while.

How much does it cost?

It scales with scope, and a flat fee before seeing your site is a guess. The cost tracks the number of templates, the WCAG level you target, whether screen-reader testing is included, and whether a retest is in the price. Ask for a fixed scope so the bill does not wander.

Can my in-house team handle it?

Sometimes, and it suits ongoing upkeep. The catch is skill. Someone has to own it and know the assistive tech, such as NVDA or VoiceOver. Most teams do not, so a common pattern is a consultant for the deep pass and in-house for the maintenance after.

Will a consultant make my site compliant?

Not on its own. A consultant shows you where you stand and what to fix. Compliance comes from doing the remediation afterwards. In Australia the Disability Discrimination Act sets the duty and the Australian Human Rights Commission treats WCAG as the yardstick, so the report is your evidence, not the finish line.

Key takeaways

A website accessibility consultant checks your site against WCAG, finds what blocks people with disability, and hands your team a ranked, fixable plan. Hire one when the stakes climb: a complaint, a tender, a custom flow, or no screen-reader skill in-house. For a first look, a free tool such as WAVE or axe plus an internal owner is a fair start, since scanners catch only about 33% of real issues. When you do hire, insist on human testing, findings by template, mapping to WCAG 2.2 criteria, and a retest in the price. In Australia the Disability Discrimination Act and the Australian Human Rights Commission make WCAG the practical benchmark. The same logic holds under the Americans with Disabilities Act. So the consultant gives you a decision and an evidence trail, not compliance by itself.

Want a scoped engagement rather than a one-click scan? That is the work we do in ADA and AHRC compliance, page by page, with a fix list you can act on.

Sources

• W3C, WCAG 2.2: https://www.w3.org/TR/WCAG22/
• W3C WAI, evaluating web accessibility: https://www.w3.org/WAI/test-evaluate/
• WebAIM, The WebAIM Million annual accessibility report: https://webaim.org/projects/million/
• Australian Human Rights Commission, World Wide Web Access, DDA Advisory Notes: https://humanrights.gov.au

Updated August 2026. Written by Sheetal Dhadial, founder of SIAGB, an AI-native consultancy in Sydney.