How Deep the Audit Goes

When someone asks what makes an audit worth paying for, this is the honest answer. The value isn't a scanner and a screenshot. It's the depth, page by page and criterion by criterion, and depth is exactly what the shortcuts skip. One thing to set up first: the audit runs two lanes in a single pass, accessibility and privacy, off the same crawl of the same site. What follows is the depth on the accessibility side. Here's what actually happens under the hood.

• Every page, crawled by our own software

  Our tool crawls your site up to three levels deep, up to 250 pages, sampling templated pages like products and articles instead of scanning thousands of identical ones. Each page is captured at desktop, tablet, and mobile sizes.

• An automated first pass on every page

  We run our automated checks on every captured page to clear the machine detectable issues fast. That is the floor, not the finish line.

• Checked against all 55 Level A and AA criteria

  We work through the full WCAGWeb Content Accessibility Guidelines, the technical standard the AODA points at 2.2 Level A and AA set, 31 Level A and 24 Level AA success criteria, or Level AAA if you ask for it. If you are counting along with a checklist site that says 56, it is out of date: success criterion 4.1.1 Parsing was removed in WCAG 2.2. Two of the 55 are exempt under AODAAccessibility for Ontarians with Disabilities Act, and we tell you which.

• Real human verification where it counts

  Automated rules only touch a minority of those criteria. On a real page a scanner reliably catches somewhere around a quarter to a third of the accessibility issues, and the rest turn on context, meaning, or whether an actual interaction works, which is a judgement no script makes. So we step through the criteria on real pages with a screen reader and a keyboard, not just a scanner reading the markup.

• Live test code, page by page

  For each criterion we run test code right in the browser to get a clear, page by page view of what passes and what fails, then hand you fix code in HTML, CSS, and JavaScript showing exactly how to remediate it.

• Evidence tied to every finding

  Screenshots, marked up drawings, and notes attached to each flagged item, so nothing is a vague you should fix this. You can see it, and so can whoever does the work.

This is the same depth behind every audit we run, and it's why the report you get is something a developer can act on line by line, not a vague score. The privacy lane gets its own equivalent depth in the same pass, trackers, consent and policy rather than criteria. If you want the full process from first look to finished report, both lanes included, that's laid out separately.

The full process, start to finish

Worth saying: we're not lawyers and none of this is legal advice. The criteria counts and the AODAAccessibility for Ontarians with Disabilities Act exemptions are what the standard and the regulation actually say, and the rest is what we see on real sites. For what your own business is obliged to do, ask a lawyer.