WCAG 1.4.11Non-text Contrast

Non-text Contrast

What is this issue?

Non-text contrast failures occur when user interface components and graphical objects essential for understanding content do not have a contrast ratio of at least 3:1 against their adjacent colors. WCAG Success Criterion 1.4.11 (Level AA) extends contrast requirements beyond text to include form field borders, icon buttons, focus indicators, chart segments, state indicators, and other meaningful visual elements.

This criterion was introduced in WCAG 2.1 to address a gap: while text contrast had been required since WCAG 2.0, many sites had invisible or near-invisible input borders, low-contrast icons, and chart segments that blended into their backgrounds. A light gray border on a white input field, for instance, makes it difficult for low-vision users to even locate the form field, let alone interact with it.

The requirement applies to two categories: user interface components (buttons, form inputs, toggle switches, checkboxes, links in their various states) and graphical objects required to understand the content (icons conveying information, chart segments, infographic elements). Decorative graphics that do not convey information are exempt.

Impact on users

For users with low vision or color vision deficiencies, a form input with a nearly invisible border is as problematic as missing text. They cannot see where to type, cannot distinguish active from inactive toggle states, and cannot identify which tab is currently selected. This transforms basic interactions into guessing games.

Low-contrast icons are particularly dangerous when they convey status information. A green checkmark and a red X that both fail the 3:1 ratio become indistinguishable for users with reduced contrast sensitivity. Similarly, chart segments that do not contrast with their neighbors make data visualization meaningless.

The impact extends to all users in challenging viewing conditions. On a mobile device in bright sunlight, low-contrast UI boundaries become invisible. Older displays with reduced color gamut exacerbate the problem. Designing for 3:1 non-text contrast benefits everyone, not just users with disabilities.

Code example

Before (non-compliant)
<!-- Low-contrast input border -->
<input type="text" style="border: 1px solid #e0e0e0;
  background: #fff;">

<!-- Icon button with poor contrast -->
<button style="background: #f5f5f5; border: none;">
  <svg fill="#ccc" viewBox="0 0 24 24">
    <path d="M3 18h18v-2H3v2zm0-5h18v-2H3v2zm0-7v2h18V6H3z"/>
  </svg>
</button>

<!-- Toggle with indistinguishable states -->
<div class="toggle off"
  style="background: #e8e8e8; border: 1px solid #eee;">
</div>
After (compliant)
<!-- Visible input border (4.5:1 ratio) -->
<input type="text" style="border: 1px solid #767676;
  background: #fff;">

<!-- Icon button with sufficient contrast -->
<button style="background: #f5f5f5; border: 1px solid #767676;"
  aria-label="Menu">
  <svg fill="#595959" viewBox="0 0 24 24">
    <path d="M3 18h18v-2H3v2zm0-5h18v-2H3v2zm0-7v2h18V6H3z"/>
  </svg>
</button>

<!-- Toggle with clear state indication -->
<div class="toggle off"
  style="background: #e8e8e8; border: 2px solid #595959;"
  role="switch" aria-checked="false">
</div>

How Scrutia detects this issue

Scrutia analyzes the computed styles of all interactive UI components and meaningful graphical elements. It measures the contrast ratio of input borders, button boundaries, icon fills, and focus indicators against their adjacent background colors. Elements falling below the 3:1 threshold are flagged with their exact ratio and a suggested color correction.

Check your site for this issue

Scrutia audits your site against WCAG criteria in minutes.

Free audit

Frequently Asked Questions

What is the difference between text contrast and non-text contrast?
Text contrast (WCAG 1.4.3) requires 4.5:1 for normal text and 3:1 for large text. Non-text contrast (WCAG 1.4.11) requires 3:1 for UI components like borders, icons, and focus indicators. Both are Level AA requirements.
Do decorative icons need to meet the 3:1 ratio?
No. Only icons that convey information required for understanding the content need to meet the ratio. Purely decorative icons adjacent to text that already communicates the same information are exempt.
Does this apply to disabled form fields?
No. WCAG 1.4.11 explicitly exempts inactive UI components. Disabled buttons, grayed-out inputs, and other inactive elements are not required to meet the 3:1 contrast threshold.
How do I measure non-text contrast?
Use the same contrast ratio tools as for text (WebAIM Contrast Checker, Chrome DevTools). Identify the boundary color of the UI component and the adjacent background color, then check the ratio. Scrutia automates this across your entire site.

Does your site have this issue?

Scrutia scans your pages against WCAG success criteria and delivers actionable fixes. Results in 5 minutes.

Run a free audit