Current ratio
4.48:1
Holds hue and chroma as close as possible to the original; only searches lightness (with gamut-safe clamping) for the minimal move that clears the ratio.
Before → After
Live UI preview
Lightness search path
original L
fixed L
zone that passes 4.5:1
Built for better interfaces
More than a contrast checker.
ContrastFixer checks text and background colors against WCAG 2.2 AA and AAA thresholds, with an APCA preview for modern accessibility workflows. When a pair fails, it searches OKLCH color space to find a minimal, gamut-safe lightness adjustment that preserves the personality of your original color.
Why color contrast matters
Low-contrast text is one of the most common accessibility failures on the web, and it affects far more people than screen-reader users alone: low vision, color vision deficiency, bright sunlight on a phone screen, and simple eye strain all make weak contrast harder to read. WCAG 2.2 Success Criterion 1.4.3 sets a 4.5:1 minimum for normal text and 3:1 for large text at level AA, rising to 7:1 and 4.5:1 at level AAA. Meeting these ratios is also a practical requirement for ADA, Section 508, and EN 301549 compliance work.
WCAG contrast vs. APCA
The WCAG 2.x formula is a simple relative-luminance ratio, which is easy to compute but known to misjudge some color pairs, especially dark-on-dark and saturated hues. APCA (Accessible Perceptual Contrast Algorithm), developed for the still-evolving WCAG 3 draft, models perceived contrast more closely by accounting for polarity and font weight. ContrastFixer reports the official WCAG ratio by default and offers an APCA Lc preview so you can sanity-check a pair against both models before they ship.