WCAG 2.3.1: Three Flashes or Below Threshold

Quick answer: Pages must not include flashing content that crosses seizure-safety thresholds.

What This Means

On ecommerce sites, Three Flashes or Below Threshold 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 holiday sale banners flash rapidly to simulate neon effects. or countdown modules strobe when inventory hits low stock., 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

• Holiday sale banners flash rapidly to simulate neon effects.
• Countdown modules strobe when inventory hits low stock.
• Embedded social ads include repeated full-screen flashes.
• Animated confetti for cart success fires intense alternating colors.

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 or soften flashing effects in campaigns and interactive celebrations.
2. Ask creative teams for static or gentle-motion alternatives to strobe-like animation.
3. Review third-party ad and social embeds before publishing them on the storefront.
4. Treat seizure-safety as a QA item for every seasonal landing page.

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 -->
@keyframes flash { 0%,100% {opacity:1;} 50% {opacity:0;} }

<!-- After -->
@keyframes pulse { 0%,100% {opacity:1;} 50% {opacity:0.92;} }

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