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
Measure each meaningful component boundary, state indicator, focus ring, and informational graphic against its adjacent color. Update the relevant CSS tokens and re-test the rendered states; a text-contrast result alone does not establish non-text contrast.
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 uses automated rules to check supported patterns in the pages reached during a scan. Some WCAG requirements need human judgment, assistive-technology testing, or access to third-party content and cannot be established by an automated scan. This criterion is generally treated as a pattern that may have a supported suggested fix. If the app can safely match the issue to supported source code, the merchant must review and approve the suggested change before anything is written, and the result is checked afterward. Otherwise the merchant should use the guidance above and independent hands-on testing. The label is not a guarantee of detection, a fix, WCAG conformance, or legal compliance.
Primary source: W3C — WCAG 2.1 Understanding 1.4.11