Skip to content
Arbor

Website accessibility audit (WCAG 2.2 AA)

We test the templates and user flows your customers rely on against the 55 success criteria of WCAG 2.2 at levels A and AA. Every issue in the report comes with evidence and a fix your developers can use.

Every audit tests all 55 of these success criteria: 31 at level A and 24 at level AA, grouped by the four WCAG principles.

Key facts

Standard
WCAG 2.2, levels A and AA
Report
HTML, tagged PDF and CSV
Starter audit
10 working days

Two sizes

We agree the scope based on the layouts and user flows you need tested.

Starter audit and Full audit compared
What is includedStarter auditFull audit
Good forA small site or one productA shop, a SaaS product or a larger site
TemplatesUp to 8Up to 20
User flows1, for example search to checkout3
DevicesDesktop and mobileDesktop and mobile
Forms, error messages and timeoutsTestedTested in more depth
Walkthrough call60 minutes60 minutes

What a template is

A template is one page layout that repeats across your site. A shop with 3,000 products has one product template, so we test it once and the fix reaches every product page. These are the templates we see most often in an online shop:

  • Home page
  • Category page
  • Product page
  • Search results
  • Cart
  • Checkout
  • Sign-in and account
  • Contact form
  • Blog post

What the report contains

The report is written in English, German or French. It arrives as HTML, as a tagged PDF and as a CSV file your team can load into its issue tracker.

  1. 1

    Summary for decision makers

    One page in plain words: what we tested, how it went, the five fixes to make first and what happens next.

  2. 2

    Scope and method

    The sample of pages, the standard, the assistive technology we used, the dates and the name of the tester.

  3. 3

    Results by WCAG criterion

    A table of every criterion and its level, showing whether it passed, failed or did not apply, with the number of issues.

  4. 4

    The issues

    Sorted by severity, then by template. Each one has its evidence and a recommended fix.

  5. 5

    Agent readiness

    Your Agent Readiness Index score and the evidence behind it, if you added it to the audit.

  6. 6

    Fix plan

    Fixes grouped by component, because fixing the header fixes it on every page.

  7. 7

    Appendices

    The test environment, a glossary and how the index works.

What we need from you

  • The pages and tasks your users rely on most.
  • One person who can answer our questions while we test.
  • A staging site if you have one, and written permission to test pages behind a login.
  • Test accounts, with the logins sent through Bitwarden Send and never by email.

We never place real orders or use real customer accounts.

Our method

We follow WCAG-EM, the W3C's method for evaluating a website. The steps, our test setup and the severity scale we use are on the How we test page.

  • Fix support

    Code examples, reviews of your pull requests and a weekly call while your developers work through the report.

  • Re-tests

    When the fixes are live, we test every reported issue again and update the report.

  • Agent readiness

    How well AI agents can read and use your site, scored with our Agent Readiness Index and backed by evidence.

  • VPAT and ACR reports

    An Accessibility Conformance Report on the VPAT template, written from the evidence of an audit of your product.

  • EU accessibility statements

    The accessibility information the European Accessibility Act asks you to publish, written from a real audit.