Short answer. Check six things before you choose: the standard they test to, how they test, whether people with disability are part of the testing, the evidence you get, the help you get after the audit, and the turnaround and price. The questions below will help you compare any provider, including us.

What to look for#

  1. The standard. Testing should be to WCAG 2.2 Level AA. For government work, ask for results mapped to AS EN 301 549 as well.
  2. The method. Manual expert testing with assistive technologies, not automated scans alone. Scans check only part of WCAG.
  3. People with disability. Ask whether people who use assistive technology every day test your key journeys, and how their findings are reported.
  4. The evidence. A dated report with findings mapped to each criterion, a plan for what does not yet conform, and something you can use in procurement or with your board.
  5. Help after the audit. Retests of fixed issues, a walkthrough with your team, and support while your developers make changes.
  6. Time and price. A clear turnaround, and either a published price or a fixed quote before work starts.

Questions to ask any provider#

  • Which version of WCAG do you test to, and do you map results to AS EN 301 549?
  • How much of the testing is manual, and which assistive technologies do you use?
  • Do people with disability test our key journeys, and how are their findings reported?
  • What exactly will we receive, and is it dated?
  • How many retests are included, and will you work with our developers on the fixes?
  • How long will it take, and what will it cost, before we commit?
  • Who will do the work, and are they separate from our build team?

How IncluD works#

  • Lived experience testing and a platform in one team. People with disability test your key journeys, and your audit history, fixes and monitoring sit in one place.
  • We work with your developers. We help your team fix what we find, and we report findings directly to you.
  • Stated turnarounds. About two weeks for a smaller website audit, three for a mid-sized one, and four to five for a large one.

We are happy to answer every question above about ourselves on a free call.

Frequently asked questions#

How much does an accessibility audit cost in Australia?#

It depends on the size and complexity of the website or app. Ask for a fixed price before work starts.

How long does an audit take?#

For most websites, between two and five weeks, depending on how many templates and journeys are in scope.

Do we need an audit or a monitoring tool?#

Usually both, at different times. An audit tells you where you stand and what to fix. Monitoring catches new issues as your content and code change between audits.

Is an automated tool or overlay enough?#

No. Automated tools check only part of WCAG, and an overlay is not evidence that your website or app conforms.

Does it matter whether a provider is disability-led?#

What matters most is that people with disability are part of the testing, and that their findings shape the report. Ask every provider how they do this.

Talk to us#

Comparing providers? Book a free 15-minute call and we will tell you honestly whether we are the right fit.