WCAG 1.4.11 Non-text Contrast
WCAG 1.4.11 Non-text Contrast explained: icons, input borders and focus indicators need a 3:1 contrast ratio. Exceptions, examples and how to test.
Table of contents
WCAG 1.4.11 Non-text Contrast is a Level AA success criterion, from WCAG 2.1. This page is part of the WCAG 2.2 success criteria guide. It explains the rule in plain English, who it helps, what passing and failing code look like, and how to test it by hand and with AccessBell, a website accessibility monitoring tool. AccessBell is not an overlay.
What WCAG 1.4.11 Non-text Contrast requires
The visual presentation of user interface components and graphical objects has a contrast ratio of at least 3:1 against adjacent color(s).
That sentence is the heart of the criterion. The exceptions and notes are in the WCAG 2.2 Recommendation and the Understanding document for 1.4.11 Non-text Contrast.
What WCAG 1.4.11 means in plain English
WCAG 1.4.3 Contrast (Minimum) is about text. WCAG 1.4.11 Non-text Contrast is about the parts of the page that are not text but still carry information: the border of a text field, the outline that shows keyboard focus, an icon button, a checked state, or the lines of a chart.
The minimum is 3:1 against the color next to the part that matters. A pale gray box on a white page often fails because the boundary is the only thing that shows where the field is. Inactive controls are excepted. So is a control whose look is left entirely to the browser and not restyled, and a graphic where a specific color is essential, such as a flag or a medical heat map.
Who WCAG 1.4.11 helps
People with low vision who can read text that passes 1.4.3 but still lose a faint border, a thin focus ring or a light icon. It also helps anyone using the page in glare. It does not set the contrast of the text inside a button. That remains 1.4.3.
Pass and fail examples
input {
border: 1px solid #d0d0d0;
background: #fff;
}
input:focus {
outline: none;
} input {
border: 2px solid #595959;
background: #fff;
}
input:focus-visible {
outline: 3px solid #1f4b99;
outline-offset: 2px;
} How to test WCAG 1.4.11
- List the controls someone has to see in order to use the page: fields, buttons that are icon-only, checkboxes, the focus outline and meaningful chart marks.
- Sample the color of the informative part and the color immediately next to it. Use the contrast checker and look for 3:1, not the 4.5:1 text threshold.
- Tab to each control and sample the focus indicator against the background behind it.
- Ignore disabled controls, and ignore a native control you have not restyled.
Testing WCAG 1.4.11 with AccessBell
AccessBell’s website accessibility monitoring tool reports text contrast under 1.4.3 when axe-core can measure it. Non-text contrast is only partly automatable: a scanner cannot always tell which pixels of an icon are the meaningful ones. Treat a clean scan as a start, then sample borders, icons and focus styles by hand.
Check your site for this with a free scan of one public page. AccessBell is a website accessibility monitoring tool, not an overlay.
Common failures on Shopify, WordPress, Wix and Squarespace
These are patterns in how the builders work. They are not counts from AccessBell scans. Where a platform hosts the screen, a merchant may not be able to change it, and an unscanned page is not a pass.
Shopify
Theme editors expose input and button colors, and a light “border” color on white product forms is a common miss. Icon-only header controls (search, cart, account) need 3:1 as well if the icon is the only thing that identifies them. Check the published theme with the Shopify checker, then sample the focus ring.
WordPress
Block themes and form plugins restyle inputs with a 1px light-gray border and set outline: none on focus. The border and the focus style are both in scope for 1.4.11. The WordPress checker will not replace a manual sample of those colors.
Wix
The Accessibility Wizard requires Level AA and does not check every element, which the Wix checklist calls out for contrast. Input underlines and icon buttons in strips are the usual misses. Publish the page and sample them, then run the Wix checker.
Squarespace
Site styles set field borders and button colors globally. Squarespace’s inclusive design guidance tells you to check contrast; the Squarespace checklist maps that to 1.4.3 and 1.4.11. A focus outline you cannot restyle still has to clear 3:1 against the section behind it, so change the background if the outline disappears.
Level and conformance
Level AA, added in WCAG 2.1, under Distinguishable. It is required for WCAG 2.1 AA and WCAG 2.2 AA. It is not required for a WCAG 2.0 AA target. Text inside the component is still covered by 1.4.3 Contrast (Minimum), which uses 4.5:1 for normal text.
Conforming at Level AA means meeting every Level A and Level AA criterion that applies, not only the ones labeled AA. See the WCAG 2.2 conformance requirements. This page explains the technical rule. It is not a legal opinion. Read the disclaimer.
Related WCAG criteria
- 1.4.3 Contrast (Minimum) (Level AA, WCAG 2.0)
- 1.4.1 Use of Color (Level A, WCAG 2.0)
- 2.4.7 Focus Visible (Level AA, WCAG 2.0)
- 2.4.11 Focus Not Obscured (Minimum) (Level AA, WCAG 2.2)
Every criterion is listed in the WCAG 2.2 success criteria guide.
Frequently Asked Questions
What contrast ratio does WCAG 1.4.11 Non-text Contrast require?
At least 3:1 between the part of the component or graphic that carries the information and the adjacent color. That is lower than the 4.5:1 ratio for normal text in 1.4.3 Contrast (Minimum).
Do placeholder text and button labels fall under 1.4.11?
No. Text, including placeholder text and the words on a button, is 1.4.3 Contrast (Minimum). 1.4.11 covers the non-text parts: borders, icons, states and graphical objects.
Are disabled buttons required to meet 1.4.11?
No. Inactive user interface components are an exception. An enabled control that is merely styled to look faint is not inactive, and it still has to meet 3:1.
What level is WCAG 1.4.11 Non-text Contrast?
Level AA, added in WCAG 2.1. A claim of WCAG 2.2 Level AA includes it. A claim that only targets WCAG 2.0 does not.
Sources
- W3C: Understanding 1.4.11 Non-text Contrast (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.