- What contrast ratio does WCAG require?
- For AA: at least 4.5:1 for normal text and 3:1 for large text (24px, or 18.5px bold) and for UI components such as icons and input borders. For AAA: 7:1 for normal text and 4.5:1 for large text. The ratio runs from 1:1 (same colour) to 21:1 (black on white).
- What is APCA and how is it different?
- APCA (Accessible Perceptual Contrast Algorithm) is the candidate contrast model for the draft WCAG 3. Instead of a symmetric ratio it gives a signed Lc value (positive for dark-on-light, negative for light-on-dark) that tracks perceived contrast better, especially for dark backgrounds and thin fonts. As a rough guide, |Lc| 90 suits preferred body text, 75 minimum body text, 60 large text and 45 headlines or large UI text. It is still a draft — WCAG 2.x is what regulations require today.
- Why does grey #888888 text fail on white?
- #888888 on #ffffff gives about 3.54:1 — enough for large text (3:1) and UI components, but short of the 4.5:1 AA minimum for normal text. The Fix-it row suggests the nearest darker grey that reaches 4.5:1, keeping the hue.
- How do the fix suggestions work?
- They search the text colour's HSL lightness in small steps, keeping hue and saturation, and return the closest lightness that reaches the target ratio against your background — so the fix stays recognisably your colour. If no lightness of that hue can pass (for example on a mid-grey background), it says so and you'll need to adjust the background too.
- Where does the eyedropper work?
- The eyedropper uses the browser's EyeDropper API, currently available in Chromium browsers (Chrome and Edge) on desktop; the button is hidden where the API doesn't exist. The colour picker and text inputs work everywhere.