Non-text Contrast: 3:1 for Icons, Borders and Focus
Also called: Graphical contrast, UI component contrast, Icon contrast, 3:1 contrast
Definition
Non-text Contrast is WCAG success criterion 1.4.11. The visual parts needed to identify user interface components and their states, and the parts of graphics needed to understand content, must have a contrast ratio of at least 3:1 against adjacent colors.
Non-text Contrast is the WCAG rule that controls and meaningful graphics must stand out from their surroundings – not just text. A light grey input border, a pale checkbox or a faint focus ring may look elegant, but people with low vision can miss them entirely. The requirement is a contrast ratio of at least 3:1.
What it means
WCAG 1.4.11 Non-text Contrast is a Level AA criterion of WCAG 2.2. It covers two groups:
| Group | What needs 3:1 against adjacent colors | Exception |
|---|---|---|
| User interface components | Visual information needed to identify a control and its state – input borders, checkbox outlines, toggle positions, focus indicators | Inactive (disabled) components; controls whose look comes from the browser and was not changed by the author |
| Graphical objects | Parts of graphics needed to understand the content – icons without text, chart lines, infographic segments | A particular presentation that is essential, e.g. a logo in its mandated brand colors |
W3C is strict about the threshold: computed values are not rounded, so 2.999:1 fails. Colors are taken from the code, not from what the screen seems to show – thin lines can look fainter because of anti-aliasing, so W3C advises avoiding very thin lines.
Text is not part of this criterion: text in images and on buttons follows color contrast (1.4.3) with 4.5:1. Hover effects are extra information and do not need 3:1 themselves. Focus indicators do – which ties 1.4.11 closely to focus visible.
W3C's failure F78 is removing or hiding the focus indicator through outline or border styles – it fails both 1.4.11 and 2.4.7.
Examples
Contrast ratios below are against a white background (#FFFFFF), computed with the WCAG formula:
| Element | Color | Ratio | Result |
|---|---|---|---|
| Input border | #767676 |
4.54:1 | Pass |
| Checkbox border | #9D9D9D |
2.71:1 | Fail |
| Input border | #CCCCCC |
1.61:1 | Fail |
| Focus outline | #0048FE |
6.25:1 | Pass |
<style>
/* Good: field border and focus ring meet 3:1 on white */
input { border: 1px solid #767676; }
input:focus-visible { outline: 3px solid #0048FE; outline-offset: 2px; }
/* Bad: border too light to find the field (1.61:1) */
.search input { border: 1px solid #ccc; }
/* Bad: focus indicator removed (F78) */
button:focus { outline: none; }
</style>
<!-- Good: icon-only button with a dark icon and a name -->
<button aria-label="Search">
<svg aria-hidden="true" fill="#1F2937">…</svg>
</button>Give input fields, checkboxes and radio buttons a border of at least 3:1, design a clear focus ring (W3C techniques G195, C40), use dark enough colors for meaningful icons – especially on an icon button – and add patterns or labels to chart segments that sit next to each other.
Rely on a pale fill to show where a field is, remove outline without a replacement, show the selected state of a toggle only with a subtle tint, or use light grey icons as the only way to identify a control.
How to check non-text contrast
Questions
What is non-text contrast in WCAG?
It is success criterion 1.4.11 at Level AA. Visual information that identifies controls and their states, and parts of graphics needed to understand content, must reach at least 3:1 against adjacent colors.
Do input borders need 3:1 contrast?
Yes, if the border is what shows where the field is. If the field has a filled background that reaches 3:1 against the page, the border itself does not need to.
Do disabled buttons need to meet non-text contrast?
No. W3C exempts inactive components. They should still look clearly disabled so nobody tries to use them.
Do logos have to meet 3:1?
Only logos whose colors are mandated by brand guidelines are exempt. A low-contrast graphic that is simply a design choice is not.
How do I measure non-text contrast?
Take the color of the border, icon or focus ring and the adjacent background color from the code and compare them. The free allyWay contrast checker shows the ratio for any color pair.
Related terms
Color Contrast: WCAG Ratios and How to Check Them
Color contrast is the difference in brightness between text or interface elements and their background, measured as a ratio from 1:1 to 21:1. WCAG requires at least 4.5:1 for normal text and 3:1 for large text.
Read definition: Color Contrast: WCAG Ratios and How to Check ThemFocus Visible: WCAG 2.4.7 and Visible Focus Styles
Focus visible means that a website shows a visible indicator – usually an outline – on the link, button or field that currently has keyboard focus. WCAG 2.4.7 requires it at Level AA.
Read definition: Focus Visible: WCAG 2.4.7 and Visible Focus StylesIcon Button: How to Give It an Accessible Name
An icon button is a button that shows only a symbol – a magnifier, a cross, three lines – and no visible text. To be accessible it needs an accessible name in code that tells assistive technology what the button does.
Read definition: Icon Button: How to Give It an Accessible NameForm Labels: Clear Labels and Instructions
Form labels are the visible texts that name what a form field expects, such as “Email address”. WCAG 3.3.2 requires labels or instructions wherever content asks for user input, including formats and required fields.
Read definition: Form Labels: Clear Labels and Instructions