WCAG 3.0 Is Coming: How the New Contrast Rules Will Change Web Design

The 4.5:1 contrast ratio has been the cornerstone of web accessibility guidelines for over two decades. If you have ever run a colour combination through a contrast checker and seen a pass or fail result based on that number, you have been using the formula introduced in WCAG 2.0 back in 2008. That formula is now being replaced.

WCAG 3.0, currently a Working Draft at the W3C, introduces a fundamentally different approach to measuring colour contrast — one that considers not just the colours themselves, but the size and weight of the text, the context in which it appears, and how the human eye actually perceives contrast on modern screens. The new method is called APCA: the Advanced Perceptual Contrast Algorithm.

WCAG 3.0 is not expected to reach full Recommendation status until 2028–2030. But understanding what is changing now — and why — is genuinely useful for designers and developers who want to build accessible interfaces that will remain compliant as the standard evolves.

What is wrong with the current contrast ratio formula?

The existing WCAG 2.x contrast ratio formula works by comparing the relative luminance of two colours. It produces a ratio from 1:1 (no contrast, same colour) to 21:1 (maximum contrast, black on white). The thresholds — 4.5:1 for normal text and 3:1 for large text — have been the compliance target under WCAG 2.0, 2.1, and 2.2.

The problem is that this formula has two known failure modes: false passes and false fails.

• False passes: Certain colour combinations pass the 4.5:1 threshold mathematically but are difficult to read in practice — particularly for people with certain types of colour vision deficiency, or on screens with high brightness or unusual gamma curves.
• False fails: Some colour combinations are highly readable in context but fail the 4.5:1 test — for example, large, bold display type where readability is genuinely high due to character size and weight, not luminance contrast alone.

The formula treats all text the same regardless of size or weight, which does not reflect how human perception actually works. A 12pt body copy paragraph and a 64pt bold headline require different contrast levels for equivalent readability — the formula does not account for this.

What APCA does differently

APCA (Advanced Perceptual Contrast Algorithm) produces a Lightness Contrast score — an LC value — rather than a ratio. The LC scale runs from 0 to approximately 106+, where higher values indicate greater contrast. Crucially, the required LC score depends on the specific text context being evaluated.

For example, under the APCA model being explored for WCAG 3.0:

• Body text (small, regular weight) requires a higher Lc score — around 60 or above.
• Large bold headings can meet accessibility requirements at a lower Lc score — around 45.
• Decorative or incidental text (e.g. a logo or purely aesthetic element) has no contrast requirement.

This contextual approach better reflects reality: a large bold heading at Lc 45 may be more readable than small body copy at the same score, because character size and weight contribute significantly to legibility.

WCAG 3.0 also replaces pass/fail with a graded model

Beyond contrast, WCAG 3.0 replaces the binary pass/fail structure of WCAG 2.x with a graded scoring system across all criteria. Instead of "passes Level AA" or "fails," interfaces will be rated on a scale, potentially labelled as Bronze, Silver, or Gold — allowing organisations to measure accessibility improvement as a spectrum rather than a cliff edge.

This is a significant philosophical shift. The current model creates an incentive to meet the minimum threshold and stop. A graded model creates an incentive to keep improving, which is more aligned with the goal of genuine inclusion.

When will WCAG 3.0 become the legal standard?

What this means for designers and developers now

You do not need to stop using the 4.5:1 ratio today — it is still the compliance target. But there are practical steps worth taking now to position your work well for the transition:

1. Continue meeting WCAG 2.1 AA standards. The 4.5:1 ratio for normal text and 3:1 for large text remain the legal benchmarks. Any interface that fails these thresholds is non-compliant today.
2. Learn to read APCA scores alongside ratios. Start familiarising yourself with APCA's Lc values now. Several tools already report both the traditional contrast ratio and the APCA Lc score simultaneously, so you can see how they compare without changing your workflow.
3. Pay attention to false fails under 2.x. If you have large, bold type that fails 4.5:1 but would pass under APCA, document this in your accessibility records. Under WCAG 3.0, it may be compliant — having the evidence ready will help when the standard transitions.
4. Treat accessibility as a spectrum, not a threshold. The graded model coming in WCAG 3.0 is more honest about reality. Building interfaces that are genuinely readable — not just numerically compliant — is good practice regardless of which version of the standard applies.