WCAG 2.1.1: Keyboard
Level AQuick answer: Everything needed to browse, configure, and buy should work with a keyboard alone.
What This Means
On ecommerce sites, Keyboard usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like variant swatches only respond to mouse clicks. or mini-cart drawers cannot be opened or closed from the keyboard., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- Variant swatches only respond to mouse clicks.
- Mini-cart drawers cannot be opened or closed from the keyboard.
- Image zoom controls are drag-only with no keyboard alternative.
- Custom dropdowns in checkout ignore arrow keys and Enter.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Use native buttons, links, inputs, and selects whenever possible.
- Add keyboard handlers that mirror pointer interactions for custom widgets.
- Verify every path to purchase works with Tab, Shift+Tab, Enter, Space, and arrow keys where expected.
- Retest after installing theme apps that replace native controls.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
<div class="wishlist" onclick="saveItem()">♡</div>
<!-- After -->
<button type="button" class="wishlist" aria-label="Save item">♡</button>FAQ
What is WCAG 2.1.1?
Everything needed to browse, configure, and buy should work with a keyboard alone.
How does WCAG 2.1.1 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with variant swatches only respond to mouse clicks. and mini-cart drawers cannot be opened or closed from the keyboard. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 2.1.1 violations?
Start by auditing the live storefront, then Use native buttons, links, inputs, and selects whenever possible.; Add keyboard handlers that mirror pointer interactions for custom widgets.; Verify every path to purchase works with Tab, Shift+Tab, Enter, Space, and arrow keys where expected.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 2.1.1 → Free ADA Compliance Scan