Skip to main content

How to Choose a Website Accessibility Consultant

If you need a website accessibility consultant, start with a simple question: what will this person actually do on your site? A good consultant tests the site by hand, with a keyboard and with real screen readers, writes a report your developers can follow, and comes back to check the fixes. A web accessibility consultant who only runs an automated scan, or who sells you a plugin and calls the job done, is not doing that work.

This guide is for teams that are about to hire someone. It covers what the job includes, how a consultant is different from a scanning tool or an overlay, what affects the cost, and the questions worth asking before you sign.

What a website accessibility consultant actually does

The job is to make your site usable for people with disabilities, and to leave your team able to keep it that way. In practice, that usually includes a few clear stages.

A manual audit. The consultant goes through your main templates and user journeys the way a person would: with a keyboard, with screen readers, and with a careful look at forms, errors, focus order, headings and alternative text. Automated scans are useful as a first pass. They are not the audit.

A report you can act on. Every issue should come with the page or component where it appears, the relevant WCAG criterion, what it means for the person using the site, and a recommended fix. If the report is just a list of rule IDs exported from a scanner, it will not help your developers much.

Support while the fixes are made. Some consultants only advise. Others also work with your development team, or fix the code themselves. Both models can work. You should know, before you start, which one you are buying.

A retest. After the fixes, the consultant checks the same journeys again. An audit without a retest leaves you guessing whether the work actually landed.

Guidance for the long term. Sites change. New pages, new forms and new features will not stay accessible on their own. A good consultant explains how to keep the work going, and can help with an accessibility statement that describes the real site, not a promise the site does not keep.

A consultant, an automated tool, and an overlay are not the same thing

These three get mixed up in sales conversations, and that is how teams waste a budget.

An automated tool is fast, and it is good at catching repeated issues such as missing alternative text or low contrast. It cannot tell you whether the alternative text makes sense, whether the focus order is logical, or whether a form error is announced clearly. Those are the problems that stop people.

An accessibility overlay or widget is a layer that sits on top of the site. It may add contrast or text-size controls, but it does not fix the code underneath. Missing labels, a broken heading structure or a keyboard trap stay where they are. We wrote in more detail about why accessibility overlays fall short.

A consultant works in the site itself. The test is manual, the fixes go into the code, and the retest confirms that a person can actually complete the journey.

What affects the cost

There is no single price for this work, and anyone who quotes before looking at your site is guessing. What usually moves the cost is:

  • How many unique templates the site has, and how complex the journeys are. A brochure site is one thing. An e-commerce checkout, a paid form or a personal area is another.
  • Whether you are buying an audit only, or also remediation support and a retest.
  • Whether the work covers the website alone, or also apps and documents.
  • The language and direction of the content. A Hebrew or Arabic site, or a site that mixes right-to-left and left-to-right text in the same form, takes more careful testing than a simple left-to-right page.
  • Whether training and an accessibility statement are part of the engagement.

Ask for a fixed scope and a clear list of deliverables before the work starts, so you can compare offers on the same basis.

Questions to ask before you hire

You do not need a long questionnaire. A few direct questions will tell you most of what you need.

  1. How do you test? Listen for manual testing with a keyboard and with screen readers, not only an automated tool.
  2. Which standard do you test against? A clear answer is WCAG 2.1 or 2.2 at level AA. If the site has to meet the Israeli standard as well, the consultant should be ready to work to IS 5568.
  3. Can I see a sample report? It should be specific enough for a developer to act on without a follow-up call.
  4. Do you fix the code, or only write the findings? Both models are valid. Know which one is in the quote.
  5. Is a retest included? If it is not, ask how the work is confirmed.
  6. How do you handle new content after the project ends? If there is no plan, accessibility will drift.
  7. Have you worked on Hebrew, Arabic or other right-to-left sites? If your audience is in Israel or in the region, this is not a nice-to-have. Direction, mixed-language forms and screen reader support in those languages need experience, not a generic English-only process.

How we work at WEB-A

A lot of the consultants you will find in English work mainly on left-to-right sites. That is not our starting point. We work on websites in Hebrew and Arabic as well as English, including right-to-left layouts and mixed-direction content, and we test them by hand.

We audit to WCAG 2.1 or 2.2 at level AA, and to Israeli Standard 5568 when the site needs to meet it. We do not install an overlay and call the site accessible.

I’m Eli Lambez, the founder of WEB-A. I am a certified digital accessibility expert from the Israel Access Association (Negishut Israel), and a certified DPO from Bar-Ilan University. WEB-A has worked with over 200 authorities, corporations and large businesses, and over 1,000 projects.

If you are looking for a website accessibility consultant, here is our website accessibility service. Tell us about the site, and we will explain the right process for it, without selling you a plugin and promising the world.

FAQ

A website accessibility consultant audits your site by hand, with a keyboard and with screen readers, gives you a report tied to WCAG, supports the fixes in the code, and retests the result. The point is a site people can actually use, not a scan score.

No. A scan finds only some of the issues, and an overlay sits on top of the site without fixing the code. Missing labels, focus order and form errors still have to be handled in the site itself.

It depends on the size and complexity of the site, whether the work is an audit only or also includes fixes and a retest, and whether apps, documents or right-to-left languages are in scope. Ask for a clear scope before you compare quotes. A price given before anyone has looked at your templates is only a guess.

Yes, but only if they actually have experience with right-to-left content. Hebrew and Arabic sites, and sites that mix those languages with English in the same form, need careful testing of direction, reading order and screen reader support. That is a regular part of our work at WEB-A.