WCAG 2.2.1: Timing Adjustable
Level AQuick answer: When a store uses time limits, shoppers need enough warning and a practical way to extend, turn off, or adjust them.
What This Means
On ecommerce sites, Timing Adjustable 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 without warning while a customer completes shipping details. or auction or flash-sale carts clear after a short countdown with no extension option., 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 without warning while a customer completes shipping details.
- Auction or flash-sale carts clear after a short countdown with no extension option.
- Account security timeouts log out users during long address edits.
- Support forms reset after inactivity with no save-progress option.
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.
- Warn users before timeout and give them a simple extend-session action.
- Avoid strict time limits unless the business case is genuinely essential.
- Persist form data so a timeout does not erase checkout progress.
- Document any unavoidable limits clearly before the task begins.
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 -->
<p>Your session expires in 60 seconds.</p>
<!-- After -->
<p id="timeout-warning">Your checkout session expires in 60 seconds.</p>
<button type="button">Extend session</button>FAQ
What is WCAG 2.2.1?
When a store uses time limits, shoppers need enough warning and a practical way to extend, turn off, or adjust them.
How does WCAG 2.2.1 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with checkout sessions expire without warning while a customer completes shipping details. and auction or flash-sale carts clear after a short countdown with no extension option. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 2.2.1 violations?
Start by auditing the live storefront, then Warn users before timeout and give them a simple extend-session action.; Avoid strict time limits unless the business case is genuinely essential.; Persist form data so a timeout does not erase checkout progress.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 2.2.1 → Free ADA Compliance Scan