WCAG 2.2 · Level A & AA

The accessibility checklist for online stores

This is what we check during a manual audit, written in plain language. Tick items off as you go, your progress is saved on this device. When you want a specialist to verify it, book an audit.

0 of 31 checks complete0%

Non-text content1.1.1AImages, icons, and image buttons have meaningful alt text; purely decorative images are hidden from screen readers.Info & relationships1.3.1AHeadings, lists, and form labels are marked up semantically, not just styled to look right.Identify input purpose1.3.5AAFields like name, email, and address use the correct autocomplete attributes.Use of color1.4.1AColor is never the only way to convey meaning, e.g. errors, required fields, or sale badges.Contrast (minimum)1.4.3AAText has at least 4.5:1 contrast (3:1 for large text) against its background.Resize text1.4.4AAContent stays usable when text is zoomed to 200%.Reflow1.4.10AANo horizontal scrolling at a 320px width; content reflows to a single column.Non-text contrast1.4.11AAButtons, form borders, and meaningful icons have at least 3:1 contrast.Content on hover or focus1.4.13AATooltips and pop-ups can be dismissed and don't vanish when you move the pointer onto them.

Keyboard2.1.1AEverything works with a keyboard alone, including menus, sliders, and modals.No keyboard trap2.1.2AFocus never gets stuck; you can tab out of every widget and modal.Bypass blocks2.4.1AA “skip to content” link lets keyboard users jump past the navigation.Focus order2.4.3ATab order follows the visual and logical order of the page.Link purpose2.4.4ALink text makes sense on its own — “View cart,” not “click here.”Focus visible2.4.7AAThe focused element always shows a clearly visible outline.Focus not obscured2.4.11AANew in 2.2Sticky headers or footers don't hide the element that has focus.Label in name2.5.3AA control's visible label matches its accessible name.Dragging movements2.5.7AANew in 2.2Anything drag-based (sliders, reordering) has a single-tap alternative.Target size (minimum)2.5.8AANew in 2.2Tap targets are at least 24×24px, or well spaced.

Language of page3.1.1AThe page declares its language with a lang attribute.On focus3.2.1AFocusing a field doesn't trigger an unexpected change of context.On input3.2.2AChanging a field doesn't auto-submit or navigate without warning.Consistent help3.2.6ANew in 2.2Help and contact options appear in a consistent place across pages.Error identification3.3.1AForm errors are described in text, not signalled by color alone.Labels or instructions3.3.2AEvery field has a persistent, visible label — not just placeholder text.Error suggestion3.3.3AAWhen an error is detected, you suggest how to fix it.Error prevention3.3.4AAFor orders and payments, changes are reversible, checked, or confirmed.Redundant entry3.3.7ANew in 2.2Don't make users re-enter information they already gave in the same flow.Accessible authentication3.3.8AANew in 2.2Login doesn't rely on a cognitive puzzle with no accessible alternative.

Name, role, value4.1.2ACustom components (dropdowns, tabs, modals) expose the correct name, role, and state.Status messages4.1.3AA“Added to cart” and error toasts are announced without moving focus.

Want a human to verify it?

A checklist gets you started. A manual audit confirms it, with the exact element and fix for every finding.

Book an audit

The accessibility checklist for online stores

Perceivable

Operable

Understandable

Robust

Want a human to verify it?