Assistive technology
Test Checkout Announcements with JAWS
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Review a checkout using JAWS in a documented Windows and browser configuration. Work in a sandbox with fictional customer and payment data. Follow one complete purchase path, including a recoverable error and a review stage.
A practical example
A test shopper changes quantity, adds a delivery address and corrects a missing postal code before confirming an order in the sandbox.
How to check it
- Identify product names, quantities and prices using JAWS navigation. Change a quantity and check how the updated total is announced.
- Move through delivery and payment controls, including any embedded payment frame. Verify that names, requirements and errors remain understandable across those boundaries.
- Review the final items, amount and destination. Test the available correction mechanism and record the completion announcement without recording sensitive payment data.
What can be missed
A payment provider can introduce a barrier outside the merchant's theme. Record the provider and frame alongside the reproduction steps so the issue reaches the correct owner.
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
- Primary workflow guidance
- WCAG 3.3.1: Error Identification
- WCAG 3.3.4: Error Prevention (Legal, Financial, Data)
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.