Testing & Tools

APCA vs WCAG Contrast: What's Different, and Which One Actually Applies

APCA (Accessible Perceptual Contrast Algorithm) is a newer contrast-measurement model, developed as part of the draft work for a future WCAG version, designed to more accurately reflect how the human eye actually perceives contrast than WCAG 2.x's existing formula does.

Why WCAG 2.x's contrast formula has known limitations

WCAG 2.x's contrast ratio (the familiar 4.5:1/3:1 numbers) is based on a relatively simple relative-luminance calculation from 2008. It's precise and easy to compute, but color-science research since then has shown it doesn't perfectly match human perception in every case — some color combinations that mathematically pass the ratio test are, in practice, harder to read than the formula suggests, and some combinations that fail the ratio test are, in practice, perfectly readable. APCA was developed specifically to address these known mismatches with a more sophisticated, perceptually-grounded model.

What APCA does differently

APCA calculates a perceptual contrast score (denoted "Lc," for lightness contrast) that accounts for factors WCAG 2.x's formula doesn't fully capture — including that light text on a dark background and dark text on a light background aren't perfectly symmetric in perceived contrast, something the older formula treats as equivalent. The result is generally considered a more accurate reflection of genuine readability than the older ratio-based approach.

Why APCA is not yet the enforceable standard

Here's the important practical distinction: APCA is part of the draft work toward a future WCAG version (informally discussed as "WCAG 3.0"), which has no fixed publication date and is not yet a published W3C standard. No law, regulation, or current WCAG version requires or references APCA today. WCAG 2.x's existing ratio-based formula remains the actual, current, legally-referenced standard for contrast — this is true regardless of how much more accurate APCA may be as a color-science model.

How AllyProof (and similar tools) use APCA today

APCA scores are reported as an informational preview metric alongside the standard WCAG contrast check — useful as an early heads-up on borderline color combinations that might be worth reviewing, but explicitly not a substitute for the actual WCAG 2.x pass/fail determination that governs real compliance today. Treat an APCA-flagged combination as "worth a second look," not as a confirmed violation the way a failing WCAG 4.5:1 ratio is.

The practical takeaway

Design and fix color choices against WCAG 2.x's 4.5:1/3:1 thresholds — that's what's enforceable today. Keep an eye on APCA as a signal for genuinely borderline cases and as a preview of where the standard may eventually move, but don't treat it as an authoritative requirement until it's actually adopted into a published, referenced WCAG version.

Official references

• Myndex: APCA

Common questions

What is APCA contrast?

The Accessible Perceptual Contrast Algorithm — a newer contrast model, developed as draft work for a future WCAG version, that scores perceptual lightness contrast (Lc) more accurately than WCAG 2.x's older luminance-ratio formula.

Is APCA required for WCAG compliance?

No. No law, regulation, or current WCAG version requires or references APCA. WCAG 2.x's 4.5:1 and 3:1 ratio thresholds remain the enforceable standard today.

Should I design to APCA or WCAG 2.x contrast?

Design and fix against WCAG 2.x's 4.5:1 and 3:1 thresholds, which are enforceable now. Treat APCA as an informational heads-up for borderline color combinations, not a confirmed requirement.