COMMERCE · ACCESSIBILITY
Ecommerce Accessibility: Audit a Shopping Journey with a Keyboard

An ecommerce accessibility review should begin with the shopping journey: find a product, choose an option, add it to the cart, correct a mistake, and reach checkout. If that journey fails without a mouse, a polished design can still exclude customers.
This practical audit gives a store owner a starting point and a way to write useful bug reports. It is not a certification of compliance and does not replace a full accessibility evaluation.
Choose a journey that includes real decisions
Select a product with at least one option, such as size, and a page with an interactive element such as a filter drawer. Use a test environment for purchase submission. Record the browser, operating system, viewport, and assistive technology when applicable.
Use Tab to move forward, Shift+Tab to move back, and the appropriate activation keys for each control. Note where focus appears. Do not use a mouse to rescue a step and then mark that step as passed.
A fictional clothing-store audit might follow this route: navigation, collection filter, product, size selector, size guide, cart drawer, and checkout form. This tests interactions that a homepage-only scan misses.
Check focus visibility and reading order
At every step, you should be able to tell which control will respond. Look for focus hidden behind a sticky header, disappearing outlines, or a tab sequence that jumps into content the user cannot see.
When a drawer or dialog opens, check that keyboard focus moves into a sensible place and can return to the control that opened it. Confirm the close control is available and that the user is not trapped. Different interface patterns have different expected behavior; document the observed sequence rather than prescribing the same key handling for every widget.
A useful bug report names the control, the action, the actual focus destination, and the expected next step. “Accessibility issue on product page” is too vague to reproduce.
Give options and forms understandable labels
A row of colored circles is not enough if its meaning depends entirely on color. The size and color controls need names and a clear selected state. A screen reader user should be able to identify the chosen option without guessing from an image filename.
For form fields, visible labels should remain available after typing begins. Placeholder text disappears and often does not provide a reliable replacement. W3C's form labeling tutorial describes associating controls with their labels.
Test the label as well as the field: clicking a correctly associated label should activate or focus its control where appropriate. Long labels and translated labels should remain readable on a phone.
Make errors and cart changes perceivable
Submit a form with a required field missing. Check whether the message explains what went wrong, identifies the affected field, and tells the user how to fix it. A red border alone does not communicate all of that.
W3C's user notification guidance explains feedback associated with controls and status updates. Apply it to the actual store behavior: adding a product should produce a perceivable result, not only a brief animation far from the current focus.
Try an unavailable size, an excessive quantity, and an invalid discount code. These are ordinary customer situations. An audit that covers only the successful path can miss the point where someone becomes stuck.
Test enlargement and small screens
Enlarge the page and check that content remains usable without essential controls being clipped. Inspect menus, product option groups, sticky add-to-cart bars, and validation messages. A fixed-height panel may work with a short English label and fail with enlarged or translated text.
Check touch targets and spacing on a real phone as well as an emulated viewport. A small close icon beside another control is harder to operate than its desktop screenshot suggests.
Use automated tools to find additional issues, then verify the shopping journey manually. An automated scan can identify some contrast and labeling problems but cannot determine whether every product option or error recovery path makes sense.
Turn findings into a release plan
Prioritize blockers first: inability to open navigation, select an option, close a dialog, or submit and correct a form. Then address repeated patterns, such as the same unlabeled control appearing on every product.
For each issue, record the URL, steps, observed result, expected behavior, and test conditions. After a fix, repeat the original steps and a neighboring scenario to catch regressions.
Accessibility improvements belong in the normal acceptance checklist for theme and section work. Use the Shopify redesign checklist when planning a broader release, or request help with a specific storefront interaction.