WCAG AA and AAA contrast thresholds without the myths

AA and AAA belong to requirements, not to colors

WCAG 2.2 organizes testable success criteria at three levels: A, AA, and AAA. Contrast (Minimum), criterion 1.4.3, is a Level AA requirement. Contrast (Enhanced), criterion 1.4.6, is a Level AAA requirement. A foreground/background pair therefore does not have an intrinsic “AA color” or “AAA color” grade. It has a measured ratio, and that ratio can be evaluated against a particular criterion for a particular piece of content.

Context changes the result. A ratio of 4.6:1 passes Level AA minimum contrast for normal text and Level AAA enhanced contrast for large-scale text, but it does not pass the 7:1 enhanced threshold for normal text. Saying only “this combination is AAA” hides the text classification and the criterion that made the statement true.

The four text thresholds in one matrix

The minimum and enhanced criteria share the same kinds of text and the same listed exceptions, but their required ratios differ. Compare the unrounded contrast result against the threshold. A displayed label rounded to 4.5:1 is not enough evidence when the underlying value is 4.48:1.

• At 3.2:1, large-scale text passes the AA minimum, but normal text fails it and neither text class passes enhanced contrast.
• At 4.6:1, normal text passes AA; large-scale text passes both the AA and AAA contrast criteria.
• At 6.5:1, normal text still falls short of the 7:1 enhanced threshold, even though it comfortably passes AA.
• At 7.1:1, both normal and large-scale text pass the minimum and enhanced contrast criteria.
• A threshold result applies to the tested rendered foreground, background, state, and text classification—not to every use of the same token.

Large-scale text has a definition, not a visual impression

WCAG defines large-scale text as at least 18 point, or at least 14 point when bold, with equivalent sizing considered for CJK fonts. W3C’s Understanding document explains that CSS uses 1pt = 1.333px, making those values approximately 24px and 18.5px. The normative definition is based on point size and boldness, not on whether the copy is a heading, appears important, uses uppercase, or occupies a wide area.

• Use the font size delivered by the author before any optional user zoom.
• Treat 18pt or approximately 24 CSS px as large-scale regardless of weight.
• Treat 14pt or approximately 18.5 CSS px as large-scale only when the text is bold.
• Check the real font and computed weight; unusually thin or unfamiliar letterforms can remain difficult to read even at the threshold.
• Retest responsive typography when a desktop heading becomes smaller on mobile.
• Classify each text style separately instead of declaring an entire component large.

Passing AA contrast is not WCAG AA conformance

A page conforms at Level AA only when it satisfies every applicable Level A and Level AA success criterion, or provides a conforming alternate version. Passing criterion 1.4.3 supplies evidence for one requirement in that larger set. It does not test keyboard access, text alternatives, labels, error handling, reflow, focus visibility, target size, language, semantics, or the many other requirements at those levels.

• Conformance is cumulative: Level AA includes all Level A criteria as well as all Level AA criteria.
• WCAG conformance applies to full web pages; a passing header or component cannot make an otherwise failing page conform.
• When a page is one step in a complete process, every page in that process must conform at the stated level.
• Only accessibility-supported ways of using technologies can be relied upon for conformance.
• A formal conformance claim is optional, but if made it must identify the version, level, scope, and relied-upon technologies required by WCAG.

This distinction matters in reports. Write “the tested text pair passes WCAG 2.2 Success Criterion 1.4.3 at 5.25:1” when that is all the evidence shows. Reserve “the page conforms to WCAG 2.2 Level AA” for a page-level assessment covering the complete applicable criteria and conformance requirements.

AAA contrast is not the same as site-wide AAA conformance

A 7:1 ratio for normal text demonstrates the numeric part of the Level AAA enhanced contrast criterion for that rendered pair. Level AAA conformance is much broader: the page must satisfy all Level A, Level AA, and Level AAA success criteria. W3C explicitly does not recommend requiring Level AAA conformance as a general policy for entire sites because some content cannot satisfy every Level AAA criterion.

• Use 7:1 normal-text and 4.5:1 large-text contrast as valuable enhanced targets where they fit the design.
• Do not downgrade a strong 8:1 pair merely because the project’s formal target is Level AA.
• Do not advertise an entire product as AAA because its design tokens pass the enhanced contrast numbers.
• Record which individual AAA criteria are met beyond the claimed conformance level.
• Test whether stronger contrast harms neither hierarchy nor comprehension, especially in dense interfaces, while keeping the normative minimum intact.

Exceptions are narrow, and adjacent contrast rules still apply

Criteria 1.4.3 and 1.4.6 exclude text in inactive user-interface components, pure decoration, invisible text, incidental text inside an image with significant other visual content, and text that is part of a logo or brand name. These categories describe the role of the content, not a convenient styling label. Secondary copy, placeholders in active fields, brand-colored article text, navigation, and ordinary captions do not become exempt merely because they are muted or associated with a brand.

• Document the reason whenever an exception is applied.
• Confirm that disabled text really belongs to an inactive control rather than an active low-emphasis state.
• Distinguish a logotype from ordinary text that happens to use a brand font or color.
• Evaluate images of text under the same text-contrast criteria unless a listed exception applies.
• Test active control boundaries, focus indicators, and meaningful graphics under Non-text Contrast where applicable.
• Ensure that color is not the only visual means of conveying information.
• Continue checking zoom, reflow, spacing overrides, semantics, keyboard operation, and assistive-technology behavior.

A contrast checker cannot reliably infer all of those roles from two color fields. It can calculate a ratio and compare it with selected thresholds. A reviewer still has to identify the content, resolve the final rendered colors, choose the correct criterion, inspect every relevant state, and place that result inside a broader accessibility evaluation.

Record evidence that another reviewer can reproduce

• Identify the URL, component, state, viewport, theme, locale, and text sample.
• Record the computed font family, size, weight, and whether the text qualifies as large-scale.
• Resolve alpha, overlays, gradients, images, and inherited values to the effective foreground and background.
• Store the full-precision ratio and the threshold used; round only the human-facing display.
• Name the exact criterion tested: 1.4.3 minimum or 1.4.6 enhanced.
• Record pass, fail, or a documented exception without turning the result into a page-level claim.
• Link the primary WCAG text and retain the review date and reviewer.
• Track remaining A, AA, and optional AAA criteria separately.

{
  "sample": "Primary button label",
  "state": "default",
  "foreground": "#FFFFFF",
  "background": "#4F46E5",
  "ratio": 6.2875,
  "text": { "sizePx": 16, "weight": 600, "largeScale": false },
  "criterion": "WCAG 2.2 1.4.3",
  "threshold": 4.5,
  "result": "pass"
}

That record says exactly what passed and can be retested after a token or typography change. Color Atlas keeps the same boundary: it calculates reproducible contrast evidence, labels the four text thresholds, and links the underlying W3C material. It does not turn one ratio into a certification. Use the evidence to support a complete page and process review.