An accessibility review of a product page should verify that a shopper can understand the item, choose options, determine price and availability, add it to a cart, and recover from an error without depending on sight, color, precise pointer movement, or perfect memory. Test the complete task on desktop and mobile rather than approving the page from an automated score alone.
Start with product understanding
Read the page with images hidden and with a screen reader. Confirm that the title, description, price, unit, availability, material facts, delivery limits, return information, and seller identity remain understandable. Decorative images should not create noise; informative images need text alternatives that convey their purpose. A complex chart or size diagram may need a fuller text explanation.
W3C's accessibility principles cover text alternatives, keyboard access, enough time, predictable behavior, mistake prevention, and assistive-technology compatibility. The principles page is an introduction, not a full conformance test, so use the applicable standard and the site's stated target for formal evaluation.
Test variants, quantity, and price changes
Use a keyboard and screen reader to choose size, color, configuration, subscription, quantity, or other variants. Each option needs an understandable name, state, and relationship to the control. Do not rely on a color swatch alone. Confirm that unavailable combinations are announced and that selecting an option does not unexpectedly move focus or submit the page.
Check whether the displayed price, discount, recurring charge, inventory message, image, and delivery estimate change together. A visual update should have a programmatic equivalent. Preserve the shopper's choice when a validation message appears, and provide a clear route to undo a selection.
Review the add-to-cart path and status
Activate Add to Cart using keyboard, touch, voice, and screen reader where supported. W3C's status-message guidance explains that messages about results, progress, and errors should be programmatically available to assistive technologies without requiring an unnecessary focus change. Verify that cart success, quantity changes, stock errors, and waiting states are announced once and remain available long enough to understand.
Do not make the shopper hunt for proof that the action worked. A changing cart icon with no text or announcement is weak evidence. If a cart drawer opens, ensure focus moves or remains predictably, the drawer has a name, the close control is reachable, and focus returns to the initiating control.
Inspect forms, errors, and time limits
Review quantity fields, postal-code estimators, personalization, sign-in prompts, and any express-checkout pre-step. W3C's forms tutorial recommends labels, logical grouping, instructions, input validation, correction help, success or error notices, and manageable stages. It also recommends avoiding time limits where possible or allowing users to turn them off or extend them when the limit is not essential.
Submit empty, malformed, and unavailable selections with harmless test data. Confirm that errors identify the field, explain the problem, and preserve valid entries. Required status, format examples, and constraints should appear before the user commits rather than only after failure. Do not use placeholder text as the only label.
Test layout, input, and distraction
Zoom text and the page, increase text spacing where relevant, rotate a mobile device, and use a narrow viewport. Check that price, controls, disclosures, and error text do not overlap or disappear. Navigate every interactive element by keyboard and confirm visible focus, logical order, sufficient target size, and escape from menus or galleries.
Pause autoplay, animation, carousels, and countdowns. Make promotional content distinguishable from product facts. Sticky banners, chat widgets, cookie controls, and advertising must not obscure focused controls or essential disclosures. Test in bright and low-light conditions where color and contrast problems can become more apparent.
Record and retest the buying task
For each finding, record the URL, product state, browser, device, assistive technology, steps, expected result, observed result, severity, and evidence. Prioritize blockers to understanding, selection, price, cart, and error recovery. Retest fixes with the same task and include disabled shoppers when feasible. The page is ready for a decision when the purchase path is reproducible and any remaining limitations are explicitly documented.
Sources
- Accessibility Principles — W3C Web Accessibility Initiative
- Understanding Success Criterion 4.1.3: Status Messages — W3C Web Accessibility Initiative
- Forms Tutorial — World Wide Web Consortium Web Accessibility Initiative