Controls need a name and a way in
The W3C Web Content Accessibility Guidelines 2.2 include requirements for keyboard access, focus visibility, text alternatives and the name, role and value of interface controls. In a retail journey, that means a search box, quantity selector or bag action should be understandable without relying on its visual position alone.
The result needs to be perceivable
A visual update is not enough if it cannot be read. WCAG 2.2 includes status-message requirements that let assistive technology present a change without moving focus. In our store concept, a bag update is announced as a demonstration action rather than a real order.
A smaller screen is not a smaller task
Reflow is covered by WCAG 2.2: the content should remain usable without losing information or function when space is reduced, subject to the criterion's exceptions. A price, quantity and qualification are part of the decision and should not disappear to make a phone layout tidier.
A baseline, not a badge
A standard tells us what needs attention; a single automated result does not establish full conformance. Keyboard use, assistive technology, reading order and real devices still need evaluation. This is an interpretation of the standard for retail design, not a claim that every requirement is already met.
Source and scope
W3C, Web Content Accessibility Guidelines (WCAG) 2.2, Recommendation 12 December 2024. Relevant criteria include keyboard (2.1.1), focus visible (2.4.7), reflow (1.4.10), name/role/value (4.1.2) and status messages (4.1.3).
Read the W3C standardOur retail application above is editorial interpretation, not a W3C endorsement or a conformance declaration.