WCAG 2.2.6: Timeouts

Quick answer: Users should know about inactivity timeouts and what data will be lost before the timeout occurs.

What This Means

On ecommerce sites, Timeouts 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 checkout sessions expire with no advance notice of data loss. or image upload tools for returns time out silently., 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

• Checkout sessions expire with no advance notice of data loss.
• Image upload tools for returns time out silently.
• Gift registry forms discard progress after inactivity without warning.
• B2B quote builders reset after idle periods with no explanation.

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.

1. Explain timeout duration and consequences before or during the task.
2. Warn users clearly before data loss and offer a way to extend the session.
3. Auto-save form progress when possible.
4. Document timeout behavior in workflows that rely on secure sessions.

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 -->
<form id="returns">...</form>

<!-- After -->
<p>This form times out after 15 minutes of inactivity. We will warn you before your data is cleared.</p>

Check if your store passes WCAG 2.2.6 → Free ADA Compliance Scan