Conformance levels measure how far criteria are met, not which barriers matter more

What it is

In a review someone says: “A is low priority; AAA is the users who actually matter.” Keyboard access and images with no text go to “later”; contrast and sign language get billed as a higher grade of care. A conformance level measures how far the criteria stack is met. It is not a ranking of which impairments or groups are more important. A, AA, and AAA are nested degrees: a claim of AA already includes all of A. It is not a list of who is worth serving.

Reading it as a star rating is a metaphor borrowed from other scales. One fewer star can still be a good product. Missing a layer of A can mean someone cannot enter at all.

Why it happens

Levels are stacked by implementation difficulty and coverage, not by moral weight. Much of A is “without this, a channel or an input is simply cut”: no text alternative, no keyboard, no minimum name. AA adds, on top of that unbroken line, contrast, captions, visible focus — conditions that let more people finish. AAA stacks costlier production (sign language, extended audio description, tighter contrast and reading level). Because the stack is inclusive, a bigger label only means “thicker, after the line already holds.” It does not mean “these users matter more.”

The second layer is asymmetric failure. An A failure is often blocking: no keyboard, and the function does not exist. An unmet AAA item is often a degraded path: a video without sign language may still be usable with captions. Translating “bigger number” into “do this first” parks the blocking items last — which is the scale used backwards.

Studying it

On a product’s critical path, tag failures in two columns: who is completely blocked, and who can still detour at a higher cost. Overlay the WCAG level labels and see whether blocks cluster at A. Do not use “count of higher-level items shipped” as the KPI for accessibility effort.

Independent variables: conformance level of the failing criterion, whether a substitute path remains. Dependent variables: whether task completion drops to zero under that failure, whether the effect is a missing channel or extra effort.

WCAG-EM sampling decides whether a page meets a claimed level. It does not weight AAA as three times A. Treating AAA items as triple-important smuggles in a weight the standard does not contain.

Where it stops holding

A product can still schedule by risk — fix the defect that stops an order — that is task consequence, not the level issuing orders. For some content (pre-recorded video for a Deaf audience) an AAA item can be more urgent than a marginal AA case. That priority comes from content type and user research; it still does not rewrite “level ≠ importance.” When criteria are mapped to P0/P1 internally, reorder by blocking, do not auto-file A as P2. Teaching A/AA/AAA as progress badges reinforces the star metaphor and has to be broken on day one.

Applying it

• Rank the backlog by “does this failure make an input or a channel completely dead,” not by how many letters are in the level tag.
• Before claiming a level, inventory every lower-level criterion it contains; missing A, there is no AA.
• Do not write “do the high levels first, backfill A later” on a roadmap — that is the degree scale used as a priority scale.
• How to check: take the current defect list, hide the level column, and re-rank only by who is blocked. If a pile of A failures jump from the tail to the head, the levels have been used as importance.

Related

• Same group: J1.02.2 Level AA is the baseline most accessibility laws actually adopt · J1.02.3 Level AAA cannot be treated as a site-wide requirement for every content type
• Nearby: J1.10 Scope of conformance claims · J1.12 Accessibility statements and conformance documentation
• Search terms: conformance level · WCAG A AA AAA · priority vs level