WebAIM Says This Gray Passes WCAG; APCA Says It Doesn't
#767676 on white passes WCAG 2 AA at 4.54:1 but scores APCA Lc 71.6, short of the Lc 75 body-text level. Why WCAG 2 and APCA disagree.
#767676 text on a white background gives a WCAG 2 contrast ratio of 4.54:1. Drop those exact colors into the WebAIM Contrast Checker — the most-linked accessibility tool on the web — and you get a green badge: AA Pass — Normal Text. Drop the same colors into the APCA reference implementation (apca-w3 0.1.9) and you get Lc +71.6, which is below Lc 75, the level APCA sets as the minimum for body text. Its font lookup accepts the pair only from 19.5 px at weight 400, and 16 px regular text needs Lc 90. Two algorithms, same hex codes, opposite verdicts at body-text size. They do not have the same standing: WCAG 2 is a W3C Recommendation, while APCA is not a W3C standard. It was developed as a candidate contrast method for WCAG 3, which is still a working draft.
This is the gap the WCAG 3 working draft exists to close. WCAG 2.1's (L1 + 0.05) / (L2 + 0.05) formula was specified in 2008 against a 1996 sRGB linearization, and the contrast-ratio thresholds were calibrated against early-2000s CRTs. The APCA documentation (Somers / Myndex) argues that the WCAG 2 ratio misjudges color pairs in both directions: some pass WCAG 2 but are hard to read, especially for low-vision readers, and some fail WCAG 2 but read well. Every mainstream consumer contrast checker (WebAIM, Coolors, contrast-ratio.com, Whocanuse) implements only WCAG 2. This tool runs both, side by side, and flags every pair where they disagree.
The 4.54 vs Lc 71.6 Trap
The WCAG 2 number for #767676 on white is 4.54:1 (worked by hand here). WCAG 2.1 SC 1.4.3 sets the AA-Normal floor at 4.5, so this pair passes by 0.04 — close, but a pass is a pass. The APCA Lc is +71.6. APCA's font lookup (fontLookupAPCA in apca-w3) works the other way round from a pass/fail threshold: give it an Lc and it returns the smallest font size that Lc supports at each weight. Four of its rows are below; what each APCA Lc level allows has the full list.
| Lc | Weight 400 | Weight 700 |
|---|---|---|
| 60 | 24 px | 16 px |
| 70 | 19.5 px | 14.5 px |
| 75 | 18 px | 14 px |
| 90 | 16 px | 14 px |
Between rows the function interpolates, and at Lc 71.6 it still returns 19.5 px for weight 400 and 14.5 px for weight 700. Body copy at 16 px regular, which is what most websites use, needs Lc 90. So APCA rejects this gray for 16 px body text and accepts it for 20 px regular or 14.5 px bold. WCAG 2 prints one number and one verdict for every size below 18 pt. APCA prints one number and asks the developer what size the text actually is.
The disagreement is not noise. Run the gray ramp:
| Foreground | WCAG ratio | WCAG AA Normal | APCA Lc | APCA 16 px / 400 |
|---|---|---|---|---|
#767676 | 4.54 | ✓ pass | +71.6 | ✗ fail |
#888888 | 3.54 | ✗ fail | +63.1 | ✗ fail |
#999999 | 2.84 | ✗ fail | +54.6 | ✗ fail |
#FFD700 (gold) | 1.40 | ✗ fail | +19.2 | ✗ fail |
#FF8800 (orange) | 2.39 | ✗ fail | +46.5 | ✗ fail |
#767676 is the boundary case the WCAG 2 ratio uniquely gets wrong. APCA agrees with WCAG 2 on the obvious losers (#FFD700, #FF8800) and disagrees on the borderline grays that real readers struggle with — the exact range where a designer is most likely to trust a green checkmark.
Asymmetric Exponents: Why Polarity Has a Sign
WCAG 2's formula is symmetric in polarity: swap foreground and background and the ratio is identical (max / min does not care which color is which). Human contrast perception is not symmetric. Dark text on a light background is measurably easier to read than light text on a dark background at the same luminance gap — APCA encodes this in two pairs of exponents and reports a signed Lc:
if (bgY > txtY) {
// BoW — dark text on light bg → positive Lc
Sapc = (bgY ** 0.56 - txtY ** 0.57) * 1.14;
} else {
// WoB — light text on dark bg → negative Lc
Sapc = (bgY ** 0.65 - txtY ** 0.62) * 1.14;
}
The exponents 0.56 / 0.57 (BoW) and 0.65 / 0.62 (WoB) are not interchangeable, and txtY and bgY use different exponents within each branch on purpose. Black text on white returns Lc +106.04; white text on black returns Lc −107.88. Same two hex codes, polarity swapped, a 1.84-point gap in absolute magnitude. WCAG 2 returns 21.0 either way and cannot tell you which polarity is more legible.
Two sRGB-to-Linear LUTs, On Purpose
The most common porting bug for either algorithm is sharing the sRGB-to-linear lookup. WCAG 2 uses the IEC 61966-2-1 piecewise function (post-2021 threshold 0.04045, not the original 1996 value 0.03928 — the change is normatively equivalent for 8-bit input but several published implementations still ship the old number). APCA uses a pure pow(c, 2.4). The two diverge below ~10/255 by enough to flip pass/fail on low-luminance pairs:
// WCAG 2.1 SC 1.4.3 (IEC 61966-2-1 piecewise)
const wcag = cs <= 0.04045 ? cs / 12.92 : ((cs + 0.055) / 1.055) ** 2.4;
// APCA G-4g (apca-w3 0.1.9)
const apca = (c / 255) ** 2.4;
Feed APCA the WCAG decode and dark colors drift: #101010 on white falls from Lc 105.45 to 103.88, and #303030 from 99.55 to 95.98. This tool keeps its own piecewise table for WCAG 2 and leaves APCA to the official apca-w3 package, so the two decodes never mix.
Color-blindness simulation needs the same piecewise decode before its LMS matrices; skipping it renders #FF0000 about 1.6 stops too dark.
Try It
Paste #767676 as the foreground and #FFFFFF as the background into the Contrast Checker. The left panel reads WCAG 2 ratio 4.54 — AA Pass (Normal Text). The APCA result reads Lc +71.6, with a minimum font size of 19.5 px at weight 400 and 14.5 px at weight 700, so 16 px regular body text is out. The banner reads "WCAG 2 and APCA disagree".
For the polarity asymmetry, set foreground #000000 on background #FFFFFF: Lc +106.04. Click Swap: now #FFFFFF on #000000 gives Lc −107.88. WCAG 2 prints 21.00 either way.