Rule
Form field boundary contrast
Form field fills and borders below 3:1 need checking against the field's other identifiers.
- Rule
non-text-contrast- WCAG 2.2
- 1.4.11 Non-text Contrast (opens in a new tab) (Level AA)
- Severity
- Serious
What it checks
Measures the boundary of text fields, text areas and restyled select menus against the background around them. The fill, each border side and an outline drawn at rest are all candidates, and the field passes when any of them reaches 3:1. A borderless field inside a snug wrapper that draws a contrasting border or fill also passes. Disabled fields are exempt.
When a person decides
This rule never fails. A boundary is only required when it is what identifies the field, and a field with a visible label and placeholder can be found without one. So a field whose fill and borders all fall under 3:1, or that has neither, is sent for review. So is a field whose boundary may come from a box shadow or background image, or uses translucent colours.
Example
Sent to review
<label for="town">Town</label>
<input id="town" style="border: 1px solid #ddd; background: #fff">
Passes
<label for="town">Town</label>
<input id="town" style="border: 1px solid #767676; background: #fff">
The engine is tested against both examples.
How to fix it
Give the field a border or fill with at least 3:1 contrast against the page around it.
Check your own pages
This rule runs in every pour audit: the browser extension, the bookmarklet, the command line and the editor. Get pour, free.