WCAG 1.4.11: Non-text Contrast
Level AAQuick answer: UI components and meaningful graphics need enough contrast so shoppers can see boundaries, states, and controls.
What This Means
On ecommerce sites, Non-text Contrast 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 input borders on checkout forms are nearly invisible against white backgrounds. or inactive and active tab states differ by subtle shades that users cannot distinguish., 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
- Input borders on checkout forms are nearly invisible against white backgrounds.
- Inactive and active tab states differ by subtle shades that users cannot distinguish.
- Graphical size-chart markers blend into the chart background.
- Carousel arrows and close icons use low-contrast strokes.
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.
- Increase contrast for component boundaries, focus indicators, and selected states.
- Review icons, charts, and custom controls—not just body text—for the 3:1 threshold.
- Use solid borders or fills for inputs that must be discovered quickly during checkout.
- Check SVG strokes and brand-outline icons on dark and light themes.
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 -->
.field { border: 1px solid #d1d5db; }
<!-- After -->
.field { border: 1px solid #4b5563; }FAQ
What is WCAG 1.4.11?
UI components and meaningful graphics need enough contrast so shoppers can see boundaries, states, and controls.
How does WCAG 1.4.11 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with input borders on checkout forms are nearly invisible against white backgrounds. and inactive and active tab states differ by subtle shades that users cannot distinguish. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 1.4.11 violations?
Start by auditing the live storefront, then Increase contrast for component boundaries, focus indicators, and selected states.; Review icons, charts, and custom controls—not just body text—for the 3:1 threshold.; Use solid borders or fills for inputs that must be discovered quickly during checkout.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 1.4.11 → Free ADA Compliance Scan