WCAG 2.2 is the current version of the Web Content Accessibility Guidelines. The W3C published it as a Recommendation on 5 October 2023 (What's New in WCAG 2.2 (W3C WAI)). If your store already works toward WCAG 2.1 AA, you are most of the way there: the earlier criteria are essentially the same, and 2.2 adds a handful of new ones. This guide explains the new level A and AA criteria in store terms. For the basics of 2.1 AA, start with our plain-English guide.
What changed from 2.1
According to the W3C, WCAG 2.2 provides 9 additional success criteria, and the 2.0 and 2.1 criteria are essentially the same, with one exception: 4.1.1 Parsing is obsolete and removed (What's New in WCAG 2.2 (W3C WAI)). Of the nine new criteria, three are at level AAA, which few sites aim for. The six at levels A and AA are:
| Criterion | Level | Where it shows up on a store |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | Sticky headers, cookie banners, chat bubbles |
| 2.5.7 Dragging Movements | AA | Price range sliders, before/after sliders |
| 2.5.8 Target Size (Minimum) | AA | Swatches, quantity buttons, footer icons |
| 3.2.6 Consistent Help | A | Contact link, chat, FAQ link |
| 3.3.7 Redundant Entry | A | Checkout and multi-step forms |
| 3.3.8 Accessible Authentication (Minimum) | AA | Customer account login |
2.4.11 Focus Not Obscured: watch your sticky bars
When an element gets keyboard focus, it must not be entirely hidden by content you added (Understanding Success Criterion 2.4.11: Focus Not Obscured (Minimum) (W3C WAI)). The W3C's own example is a sticky banner across the bottom of the page that hides focused items (What's New in WCAG 2.2 (W3C WAI)). On stores, the usual culprits are sticky headers, cookie banners, "free shipping" bars and chat buttons. Test it with the keyboard test: tab down the page and check that the focused item is always at least partly visible. A CSS fix that often helps with sticky headers:
/* Leave room for an 80px sticky header when the browser scrolls focus into view */
html { scroll-padding-top: 90px; }2.5.7 Dragging Movements: give sliders a click alternative
Anything that works by dragging needs a single-pointer way to do the same thing, unless dragging is essential (Understanding Success Criterion 2.5.7: Dragging Movements (W3C WAI)). A price filter slider can include two number fields for minimum and maximum price. A drag-to-reorder wishlist can offer "move up" and "move down" buttons. Swipe-only image carousels should also have previous and next buttons.
2.5.8 Target Size: at least 24 by 24 pixels
Targets for pointer input should be at least 24 by 24 CSS pixels, or have enough space around them, with some exceptions such as links inside a sentence (Understanding Success Criterion 2.5.8: Target Size (Minimum) (W3C WAI)). In our scan of 10 small stores, 2 had tap targets that were too small. Common examples are color swatches, the plus and minus quantity buttons in a cart and small social icons in the footer. Larger targets help everyone on a phone. See accessible variant pickers for swatches.
3.2.6 Consistent Help: keep help in one place
If your pages offer help such as contact details, a contact form, a chat button or an FAQ link, and it appears on multiple pages, it should appear in the same relative order on each one (Understanding Success Criterion 3.2.6: Consistent Help (W3C WAI)). Most themes do this already through the header and footer. Watch out for apps that show chat on some pages and not others in a different position, or product templates that move the contact link.
3.3.7 Redundant Entry: don't ask twice
Information a shopper has already entered in the same process should be filled in automatically or available to select, with some exceptions such as security (Understanding Success Criterion 3.3.7: Redundant Entry (W3C WAI)). A "billing address same as shipping" checkbox is the classic example. Shopify runs its own checkout; on WooCommerce, check any custom checkout or multi-step form plugin you have added.
3.3.8 Accessible Authentication: no puzzles to log in
Logging in should not require a cognitive function test, such as remembering a password or solving a puzzle, unless there is an alternative or a mechanism to help (Understanding Success Criterion 3.3.8: Accessible Authentication (Minimum) (W3C WAI)). In practice: don't block pasting into password fields, so password managers work; offer a login link or code by email if your platform supports it; and if you add a CAPTCHA, check it has an accessible alternative.
Check your own store in a minute or two. Our free scanner opens your homepage, a collection page, a product page and your cart in a real browser and lists the problems it can detect automatically, in plain English.
Common questions
Should I target WCAG 2.1 or 2.2?
That depends on what you have been asked for, so check any contract or legal requirement you face (and ask a lawyer if it is a legal matter). Technically, the W3C "encourages you to use the latest version of WCAG" and says the versions are backwards compatible: content that conforms to WCAG 2.2 also conforms to 2.1 and 2.0 (WCAG 2 Overview (W3C Web Accessibility Initiative)).
Does the scanner test the new criteria?
Partly. Our scanner uses axe-core, which reports small tap targets (2.5.8). Focus visibility behind sticky bars, dragging alternatives, help placement, redundant entry and login need a person to check.
Is there a WCAG 3?
WCAG 3 is a W3C draft, not a finished standard. WCAG 2.0, 2.1 and 2.2 are the existing standards, and 2.2 is the latest (WCAG 2 Overview (W3C Web Accessibility Initiative)).
Technical fixes, not legal advice. This guide explains website accessibility from a technical point of view. We are not a law firm, and nothing here is legal advice. No scan, fix or guide can guarantee legal compliance, the outcome of any demand letter or lawsuit, or protection from future claims. If you have received a legal claim, please consult a qualified attorney about it.
Sources
- What's New in WCAG 2.2 (W3C WAI)
- Understanding Success Criterion 2.4.11: Focus Not Obscured (Minimum) (W3C WAI)
- Understanding Success Criterion 2.5.7: Dragging Movements (W3C WAI)
- Understanding Success Criterion 2.5.8: Target Size (Minimum) (W3C WAI)
- Understanding Success Criterion 3.2.6: Consistent Help (W3C WAI)
- Understanding Success Criterion 3.3.7: Redundant Entry (W3C WAI)
- Understanding Success Criterion 3.3.8: Accessible Authentication (Minimum) (W3C WAI)
- WCAG 2 Overview (W3C Web Accessibility Initiative)