Resources · Explainer

What Is an Accessibility Audit — and Why It Needs a Real Screen-Reader User

“We ran a scan and it says we’re 92% accessible.” It is one of the most common sentences in accessibility — and one of the most misleading. An automated scan is a useful first pass. It is not an audit. This article explains the difference, what a real audit involves, and why the most important part of it cannot be automated.

What an accessibility audit is

An accessibility audit is a structured check of a website or app against a recognised standard — almost always WCAG, the Web Content Accessibility Guidelines. Depending on where you operate, that same work is what stands behind several legal duties: the Accessibility for Ontarians with Disabilities Act (AODA) in Ontario, the Accessible Canada Act (ACA) federally, Section 508 in the United States, and EN 301 549 in European and UK procurement. A proper audit tells you three things: what is broken, how much it matters, and what to do about it.

What an automated scan can — and cannot — do

Scanning tools read your code and flag the problems a machine can detect: an image with no alt text, text with too little contrast, a form field with no label. That is genuinely useful, and every audit should start there. But a scanner cannot judge whether the alt text actually describes the image. It cannot tell you that your checkout works in theory but takes a screen-reader user forty steps, three detours and one silent failure. It cannot hear the order your page reads in, feel where focus disappears, or notice that the error message appears somewhere a blind user will never find it. The barriers that stop real people are mostly in that second category.

What a real audit involves

  1. Agreed scope. The pages, journeys and standard are fixed with you first — for example, your checkout, your application form, or your whole public site.
  2. Automated scanning for breadth: the machine-detectable problems, across everything in scope.
  3. Manual expert review against the WCAG criteria: keyboard operation, focus order, headings and landmarks, forms and error handling, documents and media.
  4. Screen-reader testing on real tasks. A tester using JAWS, NVDA, VoiceOver or TalkBack tries to do what your customers come to do — and reports exactly where it breaks.
  5. A written report you can use. Findings in plain language, prioritised by impact, written so your developers can act on them — plus a walkthrough call to go through it together. For government and public-sector buyers, the same results can be delivered as a formal Accessibility Conformance Report (ACR) — the VPAT®-based format procurement teams request.

Why the tester being a real screen-reader user matters

There is a difference between simulating a screen reader and living with one. A daily user navigates at real speed, with the settings, habits and workarounds blind people actually use. That fluency changes what gets found: the heading structure that looks fine but reads like a maze; the button that is technically labelled and practically meaningless; the journey that passes every checkpoint and still exhausts the person taking it. It also changes the recommendations — they come from someone who knows which fixes blind users will feel, and which are paperwork.

This is the principle behind this practice. Jaan Ali is a blind/visually impaired professional, certified in JAWS by Freedom Scientific and in NVDA by NV Access, with an Accessibility Analyst role at TD Bank and years as a Specialist at Apple Canada behind him. The audit you receive is not a simulation of a blind person’s experience. It is a report of one.

What it costs, honestly

Most consultants will not talk about cost until the third meeting. Here the process is simpler: after one free discovery call, you receive a written proposal with the full scope and the full cost — before any work begins. A focused AODA Check — one key journey, up to 5 pages, manually tested, with a written report — is the fastest route to an honest answer, and full WCAG audits cover the whole site at the depth your organisation needs. If a scan is all you need, run a scan. If you need to know the truth about your website, you need the audit.

Book a consultation and we will agree on the smallest check that answers your question.

Back to Resources