Accessible navigation links
Preserve native link and button semantics so shoppers can identify destinations, submenu states, and their current location.
Skip this if Application-style command menus that intentionally implement the full application-menu keyboard pattern
Keep storefront navigation as website navigation: links go somewhere, buttons change interface state, and every control exposes a useful name and state. This lets a shopper understand the menu from a screen-reader links list, a keyboard sequence, or the visible page.
WCAG 2.2 requires each link's purpose to be determinable from its text or programmatically associated context.[1] “Shop,” “Learn more,” or an unlabeled logo can be understandable in one visual arrangement and useless when links are listed out of context.
The rest of this lesson is available once the Atlas is unlocked.