WCAG 2.4.3: Focus Order
Level AQuick answer: Keyboard focus should move in an order that matches the task shoppers are trying to complete.
What This Means
On ecommerce sites, Focus Order 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 tab order jumps from quantity selector to footer before reaching add to cart. or promo modals place hidden controls in the tab sequence before visible actions., 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
- Tab order jumps from quantity selector to footer before reaching Add to Cart.
- Promo modals place hidden controls in the tab sequence before visible actions.
- Checkout tabs move from shipping to coupon input to back-to-top links unexpectedly.
- Sticky mobile bars grab focus before the page heading and price.
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.
- Keep focus order aligned with visual and logical task order.
- Avoid positive tabindex values that create artificial jumps.
- Hide offscreen or collapsed elements from the tab order until they are available.
- Retest after adding sticky elements, drawers, and A/B testing scripts.
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 -->
<button tabindex="5">Add to cart</button>
<!-- After -->
<button>Add to cart</button>FAQ
What is WCAG 2.4.3?
Keyboard focus should move in an order that matches the task shoppers are trying to complete.
How does WCAG 2.4.3 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with tab order jumps from quantity selector to footer before reaching add to cart. and promo modals place hidden controls in the tab sequence before visible actions. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 2.4.3 violations?
Start by auditing the live storefront, then Keep focus order aligned with visual and logical task order.; Avoid positive tabindex values that create artificial jumps.; Hide offscreen or collapsed elements from the tab order until they are available.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 2.4.3 → Free ADA Compliance Scan