WCAG 2.2.3: No Timing

Quick answer: Whenever possible, users should not face time limits at all for reading, choosing, or completing store tasks.

What This Means

On ecommerce sites, No Timing 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 limited-time quizzes auto-advance before users can read each question. or order lookup forms expire after short inactivity windows., 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

• Limited-time quizzes auto-advance before users can read each question.
• Order lookup forms expire after short inactivity windows.
• Gift-builder steps reset if the user pauses too long.
• Accessibility statements rotate FAQs automatically on a timer.

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. Remove non-essential time limits from reading and form tasks.
2. Keep timed experiences optional or provide a non-timed equivalent.
3. Preserve progress indefinitely where practical during commerce flows.
4. Challenge whether countdown pressure adds business value worth the barrier.

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 -->
setTimeout(clearStep, 120000);

<!-- After -->
// No automatic timeout for this step

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