My Contrast Checker Says Fail, But the Colors Look Fine — WCAG vs APCA
It's a specific, recurring frustration among people who actually design with color day to day: you run a color pair through a contrast checker, it fails the standard 4.5:1 threshold, and yet the text looks completely fine on screen — readable, clear, no issue at all. Meanwhile a different pair passes the same check and still looks noticeably harder to read. If you've hit this and started to wonder whether the checker itself is broken, it isn't — you've run into a real, well-documented gap in how the WCAG 2 contrast formula measures color, not a bug in any particular tool.
Here's what's actually going on, and the alternative that's gaining real traction among people who design for accessibility professionally.
The WCAG 2 formula wasn't built around how human vision actually works
The contrast ratio formula behind the standard 4.5:1 and 3:1 thresholds (still the legally referenced standard almost everywhere) is a relatively simple mathematical relationship between two colors' relative luminance. It doesn't fully account for known perceptual effects — how surrounding colors, font weight, and font size all change how legible a given contrast level actually feels to a real human eye. The practical result: certain color combinations, especially involving darker mid-tones or specific hue pairings, can score a passing ratio on paper while still reading as genuinely harder to see, and the reverse also happens — some failing combinations look perfectly legible.
APCA: the alternative built to fix exactly this
APCA (Accessible Perceptual Contrast Algorithm) is a newer contrast model designed specifically to correct WCAG 2's known blind spots, incorporating font weight and size into the calculation (since a thin 12px label and a bold 24px heading have genuinely different legibility needs at the same color contrast) and using a perceptual lightness model closer to how human vision actually processes contrast, rather than the simpler relative-luminance math WCAG 2 uses. It's being incorporated into the draft of WCAG 3, the standard's eventual successor, though WCAG 2's 4.5:1/3:1 thresholds remain the legally referenced standard in most places today.
What this means practically, right now
WCAG 2 remains the standard actually cited in accessibility law and most corporate compliance requirements today, so a checker reporting a WCAG 2 pass or fail is still the number that matters for meeting a legal or contractual obligation — that hasn't changed. But if a specific color pair fails WCAG 2 and you're confident it's genuinely legible (particularly for large, bold text, where APCA and WCAG 2 diverge the most), that instinct isn't necessarily wrong; it's a real, recognized limitation of the current standard, not something to dismiss as user error. The practical approach many designers land on: treat a WCAG 2 pass as the compliance floor you need to clear, and use your own judgment (or an APCA reading, where available) as a second opinion when a result feels off.
Check your own colors
Our Contrast Checker tool tests any two colors against the WCAG 2 AA and AAA thresholds instantly, entirely in your browser.