WCAG 1.4.1: Use of Color

Quick answer: Color alone cannot carry meaning for errors, availability, price changes, or required actions.

What This Means

On ecommerce sites, Use of Color 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 sale items are identified only by red text with no 'sale' label. or required checkout fields are marked only with a red border., 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

• Sale items are identified only by red text with no 'Sale' label.
• Required checkout fields are marked only with a red border.
• Size availability uses green and gray swatches without text like 'In stock' or 'Sold out'.
• Charts in annual impact or returns reports rely only on color differences.

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. Add text, icons, or patterns wherever color communicates status or action.
2. Pair error color with inline messages and programmatic invalid states.
3. Expose inventory state in text on swatches and option labels.
4. Check analytics or finance charts for legends and labels that do not depend on color vision.

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 -->
<span class="price sale-red">$24</span>

<!-- After -->
<span class="price sale-red"><span class="sr-only">Sale price </span>$24</span>
<span class="badge">Sale</span>

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