11 items3 sectionsFor Senior designers, design system architects, accessibility leads

WCAG 3.0 Preview for Designers

WCAG 3.0 has been in working-draft for years and is still incomplete — but several pieces are stable enough to inform your design system today. The APCA contrast algorithm in particular is a big departure from WCAG 2.2 and worth understanding now, even if you're still officially auditing against AA.

References: W3C WCAG 3.0 Working Draft, APCA — Accessible Perceptual Contrast Algorithm, Silver Task Force documents

014 items

What's Changing

  1. 01
    Pass/fail binary replaced with a graded score (Bronze, Silver, Gold)
  2. 02
    Contrast measured by APCA, not the WCAG 2.x ratio formula (perceptually-based)
  3. 03
    Scope broadens beyond web to include mobile apps, native software, AR/VR
  4. 04
    Outcome-based criteria replace technique-based ones (focuses on whether users succeed, not whether you used the right pattern)

025 items

APCA Contrast — Quick Mental Model

APCA returns a value from 0 to ~108 (or negative for inverted polarity). Higher absolute value = more readable.

  1. 05
    Lc 90+ — body text minimum (replaces 4.5:1)
  2. 06
    Lc 75+ — body text non-essential (footnotes, captions)
  3. 07
    Lc 60+ — large text and bold-medium text
  4. 08
    Lc 45+ — UI controls (replaces 3:1)
  5. 09
    Lc 30+ — minimum visibility for non-essential UI

033 items

What to Practice Now

  1. 10
    Try APCA on your existing design tokens (apca-online.com) and see what surprises you
  2. 11
    Notice when WCAG 2.x passes but APCA fails (often: light-gray text on white that meets 4.5:1 but fails APCA)
  3. 12
    Build outcome-driven design specs — describe the user goal, not the pattern (lets WCAG 3 grading apply)

AccessAudit AI for iPhone

Run this on your phone.

Point your iPhone camera at any color pair to see its WCAG contrast ratio and whether it passes, in real time, on the device.

More for AccessAudit AI users