WCAG 2.4.11: Focus Not Obscured (Minimum)
Level AAQuick answer: When an element receives keyboard focus, sticky bars, chat bubbles, and overlays must not hide it.
What This Means
On ecommerce sites, Focus Not Obscured (Minimum) 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 sticky mobile buy bars cover focused size options near the bottom of the viewport. or cookie banners overlap the focused checkout button., 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
- Sticky mobile buy bars cover focused size options near the bottom of the viewport.
- Cookie banners overlap the focused checkout button.
- Chat launchers hide form fields when users tab through address inputs on mobile.
- Fixed headers cover anchor-linked help content that gains focus.
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.
- Reserve safe space for sticky UI and floating widgets when focus moves.
- Scroll focused elements into a visible region, not just to the viewport edge.
- Allow banners and drawers to be dismissed before users begin form entry.
- Test keyboard navigation on small mobile viewports with every overlay active.
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 -->
input.focus();
<!-- After -->
input.focus();
input.scrollIntoView({ block: 'center' });
FAQ
What is WCAG 2.4.11?
When an element receives keyboard focus, sticky bars, chat bubbles, and overlays must not hide it.
How does WCAG 2.4.11 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with sticky mobile buy bars cover focused size options near the bottom of the viewport. and cookie banners overlap the focused checkout button. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 2.4.11 violations?
Start by auditing the live storefront, then Reserve safe space for sticky UI and floating widgets when focus moves.; Scroll focused elements into a visible region, not just to the viewport edge.; Allow banners and drawers to be dismissed before users begin form entry.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 2.4.11 → Free ADA Compliance Scan