APCA vs WCAG 2 Contrast: Dark Mode Lc Readability Guide

Contents
- The problem: why the WCAG 2 contrast formula falls apart in dark mode
- The fix: how the next-generation APCA Lc perceptual contrast algorithm works
- WCAG 2.1 vs. WCAG 3 APCA: full comparison matrix
- 5 common mistakes when designing accessible color pairs
- The 5-step workflow for building a flawless accessible color palette
- 7 tips for applying contrast standards
- Final Decision Tree: Is This Color Pair Ready for Production?
- Web Accessibility & Color Science Key Terms Cheat Sheet
- Frequently Asked Questions
You've probably run into this: the same text and background color combination gets an opposite accessibility grade depending on which contrast formula you use.
For example, take emerald text (#1E5E3A) on a deep navy background (#0B192C). The old WCAG 2.1 formula gives it the top grade — AAA (7.04:1) — and calls it perfect. The next-generation W3C standard, APCA (Advanced Perceptual Contrast Algorithm), throws a warning instead: "not usable for body text (below Lc 40)." Flip the case and an orange button on a white background fails WCAG 2.1 (3.5:1) but passes APCA with high readability.
Here's why the WCAG 2 contrast formula, in use for more than 20 years, breaks down badly in modern dark mode and flat design — plus a plain-language look at the perceptual uniformity behind APCA, now in development as the WCAG 3 standard.
Key takeaways ① The WCAG 2.1 limitation: It uses a simple fraction of relative luminance (L), (L1 + 0.05) / (L2 + 0.05), so swapping text and background returns the identical number — a symmetric error. ② APCA's perceptual uniformity: It reflects the nonlinear behavior of the eye's photoreceptors (cone and rod cells) and applies asymmetric power-law exponents depending on whether the background or the text is brighter. ③ A dark mode readability overhaul: Color pairs that all landed at 4.5:1 in WCAG 2 spread from the 30s (poor readability) to the 70s (crisp) on the APCA Lc (Lightness Contrast) scale. ④ Font size and weight awareness: APCA is not a simple pass/fail. It gives you the Lc score you need for a given font size (px) and weight.
The problem: why the WCAG 2 contrast formula falls apart in dark mode
When building a design system, most UI designers drop a HEX code into a Figma plugin or a web contrast checker, look only for the 4.5:1 (AA pass) mark, and lock in the color pair.
But the WCAG 2 formula was built in 2008 for CRT monitors and bright, white-background web pages.
- Fatal flaw 1 (symmetry): Black text on a gray background and gray text on a black background produce exactly the same result. Real eyes perceive dark text on a light background as much higher contrast.
- Fatal flaw 2 (dark mode distortion): In dark ranges, a tiny physical difference in light output gets inflated to 4.5:1 or 7:1, so text that actually makes your eyes ache and is impossible to read still passes AAA.
The fix: how the next-generation APCA Lc perceptual contrast algorithm works
APCA (Advanced Perceptual Contrast Algorithm) is being developed by the W3C's Silver Task Force as the core visual accessibility standard for WCAG 3.0, and it turns the psychology of human visual perception into math.
1. Nonlinear exponent math on perceptual lightness Y (power-law function)
APCA converts sRGB values into perceptual lightness Y, then applies a different exponent depending on whether the background is lighter than the text (light mode) or the text is lighter than the background (dark mode):
- Light mode (dark text on a light background): Lc = (Ybg0.56 − Ytxt0.62) × 100
- Dark mode (light text on a dark background): Lc = (Ybg0.65 − Ytxt0.55) × 100
- Because the operation is subtractive and asymmetric, swapping text and background changes both the sign and the magnitude of Lc to match what human eyes actually perceive.
2. Matching spatial frequency (font size and weight)
The bolder and larger the letters, the more strongly the eye registers contrast. APCA provides guidelines for the minimum font size (pt/px) and weight (400 Regular vs. 700 Bold) that are safe to use at each Lc range.
Free · no install · just enter text and background colors to get a WCAG 2 ratio and an APCA Lc reading at the same time in one second

WCAG 2.1 vs. WCAG 3 APCA: full comparison matrix
| Comparison | WCAG 2.1 contrast ratio (current standard) | WCAG 3 APCA Lc (next-generation standard) |
|---|---|---|
| Math formula shape | Simple luminance division ratio (L1 / L2) | Nonlinear power-function exponent subtraction (Ybga − Ytxtb) |
| Symmetry (text/background inversion) | Fully symmetric (same ratio when inverted) | Asymmetric (value and sign change when inverted) |
| Dark mode accuracy | Very low (overrates contrast in dark colors) | High (rates dark-background contrast closer to perception) |
| Font size/weight awareness | Simple binary split at 18pt (24px) | Fine-grained Lc thresholds by font size and weight |
| Body text (16px) recommendation | 4.5:1 or higher (AA) | Lc 75 or higher (strong readability) |
| Large headings/buttons recommendation | 3.0:1 or higher (AA Large) | Lc 60 or higher (18px Bold or larger) |
5 common mistakes when designing accessible color pairs
- Trusting the 4.5:1 number alone: Overlooking that 4.5:1 in dark mode can still look washed out to actual human eyes.
- Ignoring the contrast loss from thin weights (Weight 300): A thin font has less visual mass, so even at the same color the Lc score needs to be at least 15 points higher.
- Leaving disabled buttons below Lc 15: Even when disabled, keep at least Lc 30 so the outline or label can still be made out.
- Overusing pure white (#FFFFFF) text on pure black (#000000) backgrounds: An extreme Lc 106 causes halation for users with astigmatism or high visual fatigue (a #121212 background is recommended).
- Skipping outdoor visibility on mobile OLED: A color pair that looks great on an indoor monitor can blow out completely under 100,000 lux of sunlight.
The 5-step workflow for building a flawless accessible color palette
- Step 1 (pull the text and background HEX codes): Note the text color and background color of the UI component you want to check.
- Step 2 (enter the colors in the WCAG 3.0 APCA Web Contrast Calculator): Type each one into the text color and background color fields.
- Step 3 (check the WCAG 2 and APCA Lc verdicts together): Compare the contrast scores the two algorithms produce, side by side.
- Step 4 (match readability tiers to font size): Check the usable grade the results panel shows for 14px, 16px, 18px Bold, and 24px headlines.
- Step 5 (lock in your design system tokens): Standardize the hierarchy — body text at Lc 75+, supporting caption text at Lc 60+, large titles at Lc 45+.
7 tips for applying contrast standards
- Use #E0E0E0 instead of pure white for dark mode body text: It eases glare and lands in the most comfortable APCA range, around Lc 80–90.
- Give focus rings at least Lc 60: For keyboard Tab users, the outline needs to differ from the background by at least Lc 60.
- Run a color blindness simulation alongside: Users with red-green color blindness need to distinguish information from lightness (Lc) difference alone.
- Buy back 10 Lc points on button text with bold weight (700 Bold): A bold font instead of a thin one keeps a slightly lower-contrast brand color readable.
- Keep glassmorphism (translucent) fills at 85% opacity or higher: When a background image shows through, pair it with a blur (backdrop-filter) and give yourself an extra +15 Lc of margin.
- The placeholder golden zone (Lc 45–55): Clearly distinct from entered text (Lc 75+) yet still readable — the ideal contrast band.
- Bookmark APCA to automate design QA: Cross-checking color pairs with our tool during design QA lets you clear accessibility certification reviews without a single issue.
Final Decision Tree: Is This Color Pair Ready for Production?
- Result A (APCA Lc 75 or higher & passes WCAG 2 AA) ➔ Perfect for body text (safe for 14px–16px regular text)
- Result B (APCA Lc 60–74) ➔ Emphasized body text and button pairings (16px bold or 18px+ recommended)
- Result C (APCA Lc 45–59) ➔ Large headlines (24px+) and large icons only
- Result D (APCA Lc below 45) ➔ Never use for body text! (Limit it to placeholders or disabled elements only)
Web Accessibility & Color Science Key Terms Cheat Sheet
- APCA (Advanced Perceptual Contrast Algorithm): A next-generation, human-perception-based contrast algorithm developed as a candidate for W3C WCAG 3.0.
- Lc (Lightness Contrast): The perceptual contrast score APCA produces (0 to 106+).
- Relative Luminance: The brightness weight the human eye perceives in the sRGB color space (0.2126R + 0.7152G + 0.0722B).
- Halation: When text is too bright against a dark background, light bleeds around the letters and reduces readability.
Frequently Asked Questions
Why did my colors pass WCAG 2.1 at 4.5:1 but get a low score in APCA?
WCAG 2.1 overestimates the brightness difference people actually perceive in dark color ranges. APCA reflects the real nonlinear response curve of human visual cells, so it judges readability more strictly and accurately.
Which standard should I follow if I need web accessibility certification right now?
The current legal requirement is WCAG 2.1 (the Korean Web Content Accessibility Guidelines, KWCAG 2.2), which sets 4.5:1 (3.0:1 for large text). But for real user experience and dark mode optimization, the global best practice is to choose color pairings that satisfy both standards.
Is the color data I enter sent to an external server?
Not at all. All sRGB gamma correction and APCA Lc formula calculations run locally in your browser's JavaScript engine in real time.
This article was adapted from our Korean original. Read the Korean original