Review checkout accessibility from product selection through order confirmation, including cart, sign-in or guest choice, address, delivery, discounts, payment, review, submission, errors, and recovery. A checkout can pass a scan while still blocking a shopper whose focus is lost, whose payment error is announced poorly, or who must repeatedly transcribe information.
Start with the complete customer journey
Define representative paths for a simple product, variant, digital item, shipping item, discount, guest checkout, account checkout, declined test payment, out-of-stock change, and session timeout. Use test mode and invented customer data. Stop before any real charge unless explicitly authorized.
W3C's forms tutorial applies to purchasing forms and recommends labels, grouped controls, instructions, validation, and feedback. Test the visible page and the programmatic structure. A field's purpose, requirement, format, and error must be available without relying only on position, color, placeholder text, or sound.
Inspect labels, groups, and input purpose
Check accessible names for cart actions, quantity, email, name, address, delivery, billing, discount, card fields, wallet buttons, review, and submit. W3C's labeling guidance explains that descriptive labels should be programmatically associated with controls, supporting screen readers, speech input, larger touch areas, and predictable layouts.
Group related controls such as delivery methods, billing choices, and card expiration. Expose required and invalid state in text and code. Use suitable input purpose and autocomplete tokens so browsers and assistive tools can help. Do not block paste into card, address, email, or authentication fields without an essential reason.
Test keyboard, focus, touch, and zoom
Complete checkout with keyboard only. Verify logical focus order, visible focus, no traps, focus return after dialogs, and announcement of dynamic cart totals. Test zoom and reflow without horizontal scrolling through ordinary content. Check target size and an alternative to dragging for quantity, address selection, or cart reordering.
W3C's WCAG 2.2 update includes focus, dragging alternatives, target size, consistent help, redundant entry, and accessible authentication. If a wallet or hosted payment frame appears, test the entire embedded experience; vendor branding does not prove accessibility in the merchant's configuration.
Reduce repetition and clarify errors
When shipping and billing match, let the shopper reuse entered information. Preserve valid fields after an error. Summaries should identify each issue and link or move focus to the affected control. Inline messages should name the field, explain what went wrong, and say how to fix it.
Test card decline, invalid postal code, expired discount, out-of-stock item, changed price, failed tax or shipping lookup, duplicate submit, network interruption, and session expiry. Do not display raw processor codes as the only explanation. Preserve the cart and entered information when safe, while protecting payment data.
Verify authentication, timing, and confirmation
Offer a supported path that does not require a cognitive-function puzzle. Allow password managers and paste. Give sufficient time, warn before expiration, and provide an extension where policy permits. A security timeout can remain, but recovery should not silently discard the cart.
After the final submit, expose a clear processing state and prevent accidental duplicate orders. Confirmation should include order identifier, items, total, delivery or access expectation, contact route, and whether payment succeeded. Announce it to assistive technology and provide a durable receipt.
Record and retest
Log device, browser, assistive technology, user need, path, expected result, observed result, severity, processor mode, evidence, owner, and retest. Include real users with disabilities where possible. Automated findings, expert review, and user observations should remain distinct.
The review passes when representative shoppers can understand costs, enter information, correct errors, authenticate, choose payment and delivery, submit once, and receive confirmation without losing the cart. Repeat after theme, cart, identity, address, tax, shipping, payment, consent, or fraud-control changes.
Sources
- Forms Tutorial — World Wide Web Consortium Web Accessibility Initiative
- Labeling Controls — W3C Web Accessibility Initiative
- What's New in WCAG 2.2 — W3C Web Accessibility Initiative