Why accessibility shapes palette decisions, not just final checks
The most common error in color accessibility practice is treating it as a final check rather than a design input. A palette built for visual appeal and then evaluated for contrast is almost always a palette that will fail — because the relationships between colors were never structured around legibility, only around aesthetic intent. The more effective approach is to treat minimum contrast ratios as a design system constraint that shapes choices from the beginning. This produces better work: not just more accessible work, but more legible, more versatile, and more durable work. A palette that satisfies contrast requirements typically also performs better in low-light conditions, on lower-quality displays, and at smaller text sizes — all contexts that affect real users regardless of whether they have documented disabilities.
Understanding WCAG contrast requirements
WCAG 2.1 defines contrast requirements in terms of relative luminance ratios between foreground and background colors. The minimum ratios are: AA requires 4.5:1 for normal text (under 18pt regular or 14pt bold) and 3:1 for large text; AAA requires 7:1 for normal text and 4.5:1 for large text. AA is the legal baseline required by most accessibility regulations worldwide, including WCAG-based standards in the EU, US, UK, Canada, and Australia. AAA is not required by most regulations but is appropriate for critical content contexts: medical information, legal documents, educational materials, emergency communications. Every design system should have a contrast matrix that shows the WCAG rating for every text/background combination in the system — this matrix is a design artifact that should be maintained alongside the palette itself.
Designing for color vision deficiencies
Color blindness simulation reveals a specific category of accessibility failure that contrast ratio testing cannot detect: distinctions that are visible to standard color vision but ambiguous or invisible to users with color vision deficiencies. Deuteranopia (inability to distinguish red-green in one mode) and protanopia (a different form of red-green deficiency) together affect approximately 8% of males and 0.5% of females. Tritanopia (blue-yellow deficiency) is rarer. The design requirement is not that every color look identical to all users, but that every meaningful use of color also conveys information through a second channel: shape, label, pattern, position, or typography. Status colors (error red, warning yellow, success green) are the most common failure point — design these to be distinguishable by lightness value as well as hue, and always accompany them with icons or text labels.
Building an accessible palette from scratch
The sequence that produces the most reliably accessible palette systems begins with functional colors before aesthetic colors. Define your text color and background color first — these set the contrast baseline that all other color decisions must work around. Select your primary interactive color (links, buttons, focus states) to meet 3:1 contrast against all backgrounds where it appears. Select your semantic status colors (error, warning, success, info) to be distinguishable from each other using lightness differentiation as the primary factor and hue as a secondary cue. Once these functional requirements are satisfied, you have a constrained space in which aesthetic color choices can be made — and those choices will be meaningfully constrained in a way that produces a system rather than a collection of individually evaluated colors.
