Two sizes
We agree the scope based on the layouts and user flows you need tested.
| What is included | Starter audit | Full audit |
|---|---|---|
| Good for | A small site or one product | A shop, a SaaS product or a larger site |
| Templates | Up to 8 | Up to 20 |
| User flows | 1, for example search to checkout | 3 |
| Devices | Desktop and mobile | Desktop and mobile |
| Forms, error messages and timeouts | Tested | Tested in more depth |
| Walkthrough call | 60 minutes | 60 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
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
Scope and method
The sample of pages, the standard, the assistive technology we used, the dates and the name of the tester.
- 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
The issues
Sorted by severity, then by template. Each one has its evidence and a recommended fix.
- 5
Agent readiness
Your Agent Readiness Index score and the evidence behind it, if you added it to the audit.
- 6
Fix plan
Fixes grouped by component, because fixing the header fixes it on every page.
- 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.