WCAG 2.2 criteria, translated into store terms
For each criterion: what it means in a shop, the failures that show up most often, how to check it yourself, and how to fix it on five platforms.
Criteria covered so far
- WCAG 1.1.1 — Non-text Content Every image that carries information needs a text equivalent; images that are purely decorative must be hidden from assistive technology.
- WCAG 1.3.1 — Info and Relationships Structure you can see — headings, lists, tables, form labels — must exist in the markup too, not be simulated with font size and colour alone.
- WCAG 1.4.3 — Contrast (Minimum) Body text needs a contrast ratio of at least 4.5:1 against its background; large text (18.66px bold or 24px regular and above) needs 3:1.
- WCAG 1.4.4 — Resize Text Text must be able to scale to 200% without losing content or functionality.
- WCAG 2.1.1 — Keyboard Everything a customer can do with a mouse must also be possible with a keyboard alone.
- WCAG 2.4.2 — Page Titled Every page needs a unique title element that describes what the page is about.
- WCAG 2.4.4 — Link Purpose (In Context) Where a link goes should be clear from its text, or from the immediate context around it.
- WCAG 2.4.7 — Focus Visible When a control receives keyboard focus, there must be a visible indicator showing where that focus is.
- WCAG 2.4.11 — Focus Not Obscured (Minimum) When a control receives keyboard focus, it must not be completely hidden behind other content such as a sticky header or a cookie banner.
- WCAG 2.5.8 — Target Size (Minimum) Interactive controls must be at least 24 by 24 CSS pixels, unless they have enough spacing around them or an equivalent larger control exists elsewhere on the page.
- WCAG 3.1.1 — Language of Page The page's language must be declared in the markup: <html lang="de">.
- WCAG 4.1.2 — Name, Role, Value Every interactive element must expose a name (what it is), a role (what it does) and its state (expanded, selected) to assistive technology.
What this page covers
What follows is the practical meaning of a WCAG 2.2 success criterion. Automated tests catch only a portion of accessibility issues, so a clean scan result does not mean compliance. Platform paths vary by version and theme.