WCAG e-commerce audit: scope, method and deliverables

1. Define the scope

Sample by template, not by URL: home, category/listing, product (simple and with variants), search results, cart, cart drawer, account/login, checkout steps, confirmation, key content pages (shipping, returns, contact), and any custom widget (size guide, store locator).

2. Define the journeys

At minimum: find a product → choose options → add to cart → review cart → provide details → reach payment. Test with keyboard only, with a screen reader (NVDA/JAWS on Windows, VoiceOver on macOS/iOS, TalkBack on Android) and at 200–400% zoom.

3. Run automated checks first

Automated engines such as axe-core quickly surface a large share of detectable issues: missing names and labels, contrast, invalid ARIA, structure. Use them to clear the obvious problems before experts spend time on judgement calls.

4. Manual evaluation

Experts check what tools cannot: meaningful alternatives, focus order logic, instructions, error suggestions, consistent navigation, timing, motion, and assistive-technology behaviour.

5. Report and prioritise

Group findings by component, map them to WCAG success criteria, rate impact on the purchase path, and estimate effort. A good report gives developers code-level guidance.

6. Keep it from regressing

Once fixed, monitor the automatable part continuously so the next release does not undo the audit.