Reviewed September 30, 2026
Accessible online stores
A store fails WCAG at the moment a shopper cannot reach a product, understand the price, or complete checkout without a mouse. Test those flows first. They are the service the business offers to the public.
What has to work on a product listing?
- Product name, price, and rating are text, not baked into the product photo.
- Filter and sort controls are buttons or links with names, and the result count updates in text.
- Color swatches include the color name. Color alone does not identify the variant (success criterion 1.4.1).
- Infinite scroll also offers a paging control so keyboard users are not stuck loading more items.
- WCAG 2.2 success criterion 2.5.8 (Target Size, Minimum, Level AA) asks for a 24 by 24 CSS pixel target, with exceptions for inline links and targets that have enough space around them.
What has to work in the cart and at checkout?
Quantity fields have visible labels. Removing an item is a button named with the product, such as “Remove wool coat”, not an unlabeled icon. Checkout errors follow the form rules: name the field and how to correct it. Payment fields inside an iframe still need labels in that frame. A time limit on the cart must be adjustable under WCAG 2.2.1 unless the limit is essential.
WCAG 2.2 success criterion 3.3.7 (Redundant Entry, Level A) says not to ask for the same information twice in one process. Offer a control to use the shipping address as the billing address. Success criterion 3.3.8 covers sign-in: do not block paste, and do not make a memory test the only way to authenticate.
How do you test a purchase path?
Unplug the mouse. Search, filter, add to cart, change quantity, enter an address, and reach payment using only the keyboard. Focus has to stay visible and must not be trapped in a dialog or a cart drawer. Then repeat the same path with a screen reader and confirm every total is announced after it changes.
Drag-and-drop to reorder a cart or a filter fails WCAG 2.2 success criterion 2.5.7 (Dragging Movements, Level AA) unless there is a single-pointer alternative, such as buttons to move an item up or down. That rule is explained on the dragging movements page.
Which pages are worth auditing first?
Home, search results, a product template, the cart, and checkout cover most of the revenue path. A fix in the product template applies to every product. A fix that lives only on one handmade landing page does not. Include the account and address-book forms if returning customers have to use them to pay.
Questions and answers
What should you test first on an online store?
Test the path a shopper uses to buy: search or browse, filter, open a product, add it to the cart, change quantity, enter an address, and pay. Do that with only a keyboard, then again with a screen reader. A store fails at the moment a shopper cannot finish that path.
Do product photos need alt text?
Yes, when the photo conveys something the text does not, such as color or pattern. The product name and price should be real text, not baked into the image. If the name and price are already text next to the photo, the alt can be a short description of the photo, or empty if the photo adds nothing.
How should a remove button in the cart be named?
Name it with the product, such as “Remove wool coat”, not an unlabeled icon. Quantity fields need visible labels. When a total changes, the new amount has to be available as text, and a screen reader user needs to hear that it changed.
Does ADA Title III apply to online stores?
The U.S. Department of Justice says the ADA covers the websites and apps of businesses open to the public. An online store that sells to the public is in that group. Title III does not name WCAG in a regulation the way the Title II rule does for governments. WCAG 2.2 Level AA is the current W3C Recommendation teams use as the technical target.
Related guides
Ask for a review of a specific page
Send the URL and the template you care about. The reply names the highest-risk WCAG failures and the order to fix them.
Request an audit