A11y Guideline

How it works in practice

A design team is checking a new pricing page against WCAG success criterion 1.4.3 Contrast (Minimum), a Level AA rule. The body text sits at 4.5:1 and passes, but a row of light-grey captions measures 3.1:1 and fails. The guideline gives the test a hard number, so the disagreement resolves on measurement rather than taste. The 4.5:1 threshold was chosen to compensate for the contrast-sensitivity loss of roughly 20/40 vision🔭VisionStrategyA long-term aspirational statement of the future stateView reference →, so the rule encodes a specific human need🫀NeedUserA user need, pain, desire, or constraintView reference →, not an arbitrary figure.

Accessibility guideline vs. its neighbours

• Accessibility standard: the standard is the full POUR-structured document and its conformance level; the guideline is one criterion within it. Many guidelines roll up into one standard.
• Accessibility issue: a guideline is the rule; an issue is a specific place where the product breaks that rule. The grey captions above are an issue against the 1.4.3 guideline.
• Design guideline📌Design GuidelineDesign SystemA design usage guidelineView reference →: a design guideline is an internal house rule about how the team prefers to build (spacing, tone, component usage). An accessibility guideline is an external, standardised requirement with a conformance level attached. They can reinforce each other, and they answer to different authorities.

In the graph

In the Unified Product Graph, an accessibility guideline lives under its parent standard, attached through a11y_standard_contains_a11y_guidelineA11y StandardcontainsA11y Guidelinehierarchy. That single edge does the structural work: it keeps each criterion bound to the version and conformance level it belongs to, so a guideline never floats free of the standard that defines it. Issues then reference the guideline they violate, which lets a team trace any failure straight back to the exact rule and the standard above it.