Skip to content
Pandus
en Change language
Menu

Website accessibility audit: automated check, manual test or full audit?

Updated October 13, 2026 · 5 min read

An accessibility audit is a structured review of a website against WCAG, done by people with tools – not just a scan. An automated check finds the problems that can be detected in code; a manual test shows whether real tasks, such as buying a product, work with a keyboard and a screen reader; a full audit combines both and assesses every relevant WCAG criterion. For most online shops the sensible order is: automated check first, fix, then a manual test of the key flows.

Our service is the automated part: an automated check, not a full audit, and not legal advice.

Three levels of accessibility testing

Automated check Manual test of key flows Full audit
What happens software scans pages against rules an expert completes tasks with keyboard, zoom and a screen reader automated scan plus expert review of every relevant WCAG criterion
Finds missing alt text, low contrast, unlabelled fields, buttons without a name, missing language keyboard traps, invisible focus, confusing error messages, unusable widgets both, plus content and structure issues
Speed minutes, repeatable weekly days longer, depends on scope
Good for a first picture, monitoring after every update checkout, registration, search relaunches, procurement, disputes

How much automation catches depends on the study. The UK Government Digital Service found that the best single tool detected about 40% of deliberately planted barriers, all tools together 71%. Deque measured 57% of issues by volume in its audits. Either way, a scan alone is not the whole picture.

When an automated check is enough to start

An automated check is the right first step if you:

  • want to know where you stand before spending a larger budget,
  • need a prioritised list for your developers or agency,
  • want to see quickly whether a theme or plugin update introduced new problems.

Start with one page in the free check, or check up to 20 pages with the one-off express report. What the scan does and does not cover is explained on how it works.

When you need a manual test or a full audit

Plan a manual test when:

  • the automated issues are fixed and you want to know whether customers can actually complete a purchase,
  • you are launching a new theme, checkout or app,
  • a customer has reported a barrier and you want to understand it,
  • a business customer or a public tender asks for a documented review.

A full audit is worth it for larger relaunches or when you need a detailed report per WCAG criterion. Ask the provider which standard they test against (WCAG 2.2 AA, and EN 301 549 for the EU), which pages and flows are in scope, which assistive technologies they use, and whether a retest after fixes is included.

How to prepare your shop

Whoever tests, preparation saves time and money:

  1. List the key flows: search, category with filters, product with variants, cart, checkout up to payment, registration and login, contact form.
  2. Pick representative templates, not every page: one product page stands for thousands that use the same template.
  3. Run an automated check first and fix what it finds. A manual tester should not spend paid hours on missing alt text.
  4. Provide test access: a test account, a test payment method, and the cookie banner in its real state.
  5. Write down your platform: Shopify, WooCommerce, PrestaShop, Shoptet, or custom – fixes differ.

The WCAG 2.2 checklist shows which criteria matter most for shops.

What an audit does not do

An audit, like an automated check, does not make your site accessible on its own – the fixes do. And neither replaces a legal assessment of whether the EAA applies to you; for that, start with who does the EAA apply to. Be cautious with offers that promise a "certificate" or full conformity after a scan, or that sell an overlay widget instead of fixing the code; why overlays fall short is explained in accessibility overlays.

How we fit in

We check your site automatically against WCAG 2.2 AA, explain each problem in plain language with fixing steps for your platform, and monitor the site weekly so that fixed problems stay fixed. Agencies can deliver the reports under their own brand. A manual review can be ordered separately and is not part of a subscription – write to us via the contact form and describe your shop and the flows you want tested.

Frequently asked questions

Is an automated accessibility check the same as an audit?

No. An automated check scans the code for problems that can be detected by rules, such as missing alt text or low contrast. An audit adds manual testing with a keyboard, zoom and screen readers and an expert assessment of every relevant WCAG criterion.

Do I need a full audit for the EAA?

The law does not prescribe a specific type of test. Many shops start with an automated check of the key pages, fix the obvious problems and then have the checkout and other key flows tested manually.

Do you offer manual testing?

Our service is an automated check with weekly monitoring and reports. A manual review can be ordered separately; it is not part of a subscription. Write to us via the contact page.

Sources