Start by checking whether a shopper can navigate, choose options, add a product and complete checkout using a keyboard and assistive technology. This checklist covers what to test first, using only your keyboard and your browser. It is a preliminary review, not a complete conformance assessment.
General information, not legal advice. This checklist uses WCAG 2.2 Level AA as a technical reference; it does not determine which laws or contractual requirements apply to your store.
1. Keyboard only (15 minutes)
Put the mouse away. Press Tab to move forward, Shift+Tab to go back, Enter and Space to activate. Try to buy a product.
- Can you open the main menu and reach every link in it?
- Can you pick size and color, change quantity, and add to cart?
- Can you open and close the cart drawer, pop-ups and the cookie banner with the keyboard? (A reachable close button matters most; Escape closing dialogs is a helpful convention.)
- Can you always see where you are? WCAG 2.4.7 requires a visible keyboard focus indicator (it doesn't have to be an outline).
- Do you ever get stuck inside something (a carousel, a chat widget, a video)?
2. Images and product media (10 minutes)
- Informative images have useful text alternatives that say what a shopper needs to know: “Navy wool beanie, folded cuff, front view”, not the file name or “image”. Decorative or redundant images should be ignored by assistive technology, and linked images need a name that describes the link.
- Text inside images (sale banners, size charts) is also available as real text.
- Videos have captions. Recommended: nothing autoplays with sound. (WCAG 1.4.2 specifically requires a way to pause, stop or control audio that plays automatically for more than three seconds.)
3. Forms and checkout (10 minutes)
- Every field has a visible label, not only placeholder text that disappears.
- Error messages say what is wrong in words (“Enter a 5-digit ZIP code”), not just a red border.
- Required fields are marked in text, not only by color.
- Discount-code, newsletter and search fields are labeled too.
4. Color, text and zoom (10 minutes)
- Text contrast is at least 4.5:1 (3:1 for large text). Light gray on white and text on photos are the usual failures.
- Prices, sale badges and stock status don't rely on color alone.
- At 200% text size, nothing is lost or stops working. Separately, test reflow at a 320 CSS-pixel-wide window (about 400% zoom on a 1280-pixel screen): content shouldn't need sideways scrolling, except things that genuinely need two dimensions, like large tables or maps.
- Buttons and controls are big enough to tap: WCAG 2.2 generally asks for 24 by 24 CSS pixels, or enough spacing, with exceptions such as links inside a sentence.
5. Structure (10 minutes)
- Recommended: each page has one main heading (the product or collection name) and sensible subheadings.
- Link and button names make sense on their own: “Add Navy Beanie to cart”, not a bare icon.
- The page title in the browser tab is specific to the page.
- PDF size charts, care guides and policies are tagged PDFs. Check one with the free PDF quick check.
About overlay widgets
Don't treat installing a widget as proof of accessibility. Test the actual shopping journey and fix the barriers you find.
What an audit adds
An audit covers an agreed sample of page types and complete user journeys (for example home, collection, product, cart and checkout), with automated checks plus manual evaluation and the scope and limitations stated. Your developer gets one list: each issue, the element, the WCAG criterion and a suggested fix, ordered by impact.
Want your store audited?
I audit Shopify, WooCommerce, Squarespace, Wix and custom stores against WCAG 2.2 AA (automated axe-core scan plus manual keyboard, focus, zoom, form and screen reader checks) and deliver a prioritized fix list. No overlays and no compliance certificates. Hire me on Upwork or email aaron.signalfeed@gmail.com.