User journeys
Audit an Ecommerce Purchase Journey
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Scope a purchase from product discovery to confirmation, including variants, stock changes and payment-provider boundaries. Use a sandbox and define which purchase routes are representative of the store.
A practical example
A customer selects a size, adds two items, changes delivery and corrects a payment-entry error.
How to check it
- Map the product, cart, delivery, payment and review states. Include empty-cart, unavailable-variant and invalid-discount cases that affect the chosen route.
- Complete the route with the keyboard and a screen reader. Check names, focus, errors and announcements when quantities, availability or totals change.
- Review and correct the order before a permitted test confirmation. Record barriers with the step, provider and state so fixes can be assigned accurately.
What can be missed
Testing only the homepage or product page misses the process that creates the purchase. A successful visual purchase is not evidence for nonvisual completion.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.