On time or it's free

The Accessibility Audit

A ranked report of the accessibility problems on up to five page designs and 50 pages of your site, found by scanner and by hand, with who can fix each one and in what order.

A customer wrote to say your booking form does not work with a screen reader, or a buyer's supplier questionnaire asked about accessibility. Before you pay anyone to fix anything, you want to know how much of your site has the problem and what fixing it involves.

We scan up to 50 of your pages with axe-core and test up to five page designs by hand, with a keyboard and the NVDA screen reader, against WCAG 2.2 Level A and AA. We read your site the way a visitor does and change nothing, so the audit works on Wix, Squarespace and WordPress page builders as well as hand-built sites and web apps.

Your report ranks each problem by how badly it blocks people and how many pages it touches. It then names who can fix it: The Accessibility Alignment for a page design, a developer or designer day, your editors, or the company behind a widget. You book the fixes in the order the report gives.

A scanner finds only part of what goes wrong, so a person tests each design too. The report shows which criteria we checked and how. It does not certify your site or call it compliant, because a sample cannot prove the pages we did not open are clean.

What's included

  • Up to 50 of your pages scanned against the WCAG 2.2 A and AA rules a machine can test, at desktop and phone widths, with the serious results confirmed by a person
  • Up to five page designs tested by hand with a keyboard and the NVDA screen reader, the way someone who cannot use a mouse reaches your menus, forms and pop-ups
  • Your header, menu, footer and cookie banner checked once for the whole site, with navigation and help compared across your designs
  • Each problem ranked by how badly it blocks people and how many pages it touches, so you know what to fix first
  • A fix plan naming who fixes what: the page designs to book for The Accessibility Alignment, in order, and the findings to hand a developer, a designer, your editors or a widget vendor
  • A map of all 55 criteria showing which we checked and how, so nobody mistakes a sample for a clean bill of health
  • The report as a PDF, the findings as a spreadsheet ready for your tracker, and written answers to one round of questions

How it works

  1. 01

    Book and send access

    Book online with your ABN or NZBN. We tell you exactly what access and material we need; the clock starts once we have it.

  2. 02

    We do the work

    An experienced employee who specialises in this task works through it, and asks before anything outside the scope.

  3. 03

    Delivered with evidence

    You get everything listed on this page, with a written account of what was done.

Before you order

Have these ready so we can start the moment you order. The delivery clock only runs while we have them.

  • Ownership of the site, or written permission from its owner for us to test it
  • The site address, and whether it is your live site or a staging copy
  • Up to five page designs to test, each with the address of one page that uses it
  • For pages behind a login, a separate test account for each role (up to two) that signs in without an MFA code or CAPTCHA
  • If the site sits behind Cloudflare or similar bot protection, someone who can allowlist our browser

Who it's for

Site owners and product teams who have been asked about accessibility and want to know where their site stands, and what to fix first, before paying for fixes.

Questions

How fast is delivery?

Standard delivery is within 33 weekday hours (≈ 3 working days); express (within 20 weekday hours, ≈ 2 working days) costs 25% more. The clock pauses while we cannot reach a page, for example while you allowlist our browser or repair a test login, so a hold-up at your end never eats into your deadline.

How is this different from The Accessibility Alignment?

The Alignment takes one page design, tests it against all 55 criteria with two screen readers, fixes the failures in your code and records the result for every criterion. The audit covers up to five designs in less depth and fixes nothing. Its report tells you which designs need the Alignment and in what order, and which problems belong to a developer, a designer or a vendor instead.

Does this make us compliant, or give us a VPAT?

No. We do not issue VPATs, accessibility statements, certificates or legal opinions. We test a sample, and scanners catch only a minority of accessibility problems, so the report never marks a criterion as passed. It lists what we found, and its coverage map shows which criteria we checked and how.

Do you need access to our code or admin?

No. We read your site as a visitor does and change nothing on it. On a live site we never submit a form with real details, place an order or create an account. If some pages need a login, you create a test account for us, and we delete its details when we deliver.

Which tools do you use?

axe-core, the open-source engine Google's Lighthouse also uses, run through Playwright on each page at desktop and phone widths. A person then checks each design with a keyboard and with NVDA on Windows. We skip the Lighthouse score, because it turns the same automated checks into a number that reads like a grade.

Our site has more than five page designs. What then?

Add a second audit to the same order. Each audit covers five more designs and 50 more pages, and you get one combined report with your header and menu checked once.

Will you fix what you find?

This service fixes nothing; the fix plan routes each problem. Page designs go to The Accessibility Alignment, and custom components or page-builder sites go to the developer day for your stack, such as The WordPress Developer Day or The Front-End Developer Day. Brand colours that fail contrast go to The Designer Day, and wording goes to your editors. A re-test after the fixes is a new audit.

Often booked alongside