Non-text Contrast
User-interface components and graphical objects required to understand the content must have at least 3:1 contrast ratio against adjacent colors.
What it requires
WCAG 2.1 SC 1.4.11 extends the 4.5:1 text-contrast requirement to non-text UI: button borders, form input outlines, focus indicators, icons, and graphical elements that convey information (chart segments, status badges).
The 3:1 ratio is measured against the immediate adjacent color — so a pale-grey button border on a white background fails, but the same border on a darker section background may pass. Inactive ("disabled") UI is exempt; informative graphics are not.
Common Shopify failure
Theme `<input>` borders rendered in a 5% darker grey than the page background — common in minimalist themes. Disabled-style "Add to cart" button with `#cccccc` text on white. Pie-chart product comparison widgets where adjacent slices use indistinguishable shades.
How to fix it
AccessComply's ColorContrastAgent extends 1.4.3 detection to UI elements: identifies sub-3:1 component borders, focus rings, and informational icons, then writes fixes to your theme's CSS variables preserving brand hue while raising lightness.
Merchant QA checklist
- Scan the storefront page where this pattern appears: product pages, collection pages, cart drawer, customer-account pages, and any landing page built with theme sections.
- Confirm the issue is fixed in the rendered browser output, not only in the Liquid file. Shopify section settings, app blocks, and third-party scripts can reintroduce the same 1.4.11 failure after a theme edit.
- Re-test the affected component with keyboard navigation and a screen-reader accessibility tree before publishing the theme, especially when the fix changes markup or ARIA attributes.
How AccessComply handles it
AccessComply treats WCAG 1.4.11 as a rendered-storefront issue first. The scanner checks the live DOM and computed styles, maps the finding back to the Shopify theme file that produced it, then classifies the fix as a safe automatic fix. When automation is safe, the app writes the smallest theme-code change needed and keeps the original theme backup available. When merchant judgment is required, the issue is surfaced for manual review instead of pretending the page is fixed.
Primary source: W3C — WCAG 2.1 Understanding 1.4.11