Accessible does not mean beige.
Accessibility is not a ban on personality. It is a discipline: make text readable, states distinguishable and information understandable before adding visual drama.
Some teams hear “accessible colour contrast” and picture a grey interface with one approved blue button. That is not accessibility. That is a failure of imagination.
Contrast is a relationship
The WCAG minimum contrast guidance is 4.5:1 for normal text and 3:1 for large text. Those numbers are useful checks, but they do not choose the palette for you. They tell you whether a foreground and background can carry information together.
Start with the brand colours, then build usable tonal steps around them. The bright campaign green may work brilliantly as a large field or illustration detail, while a darker green is needed for body text. Both can belong to the same system.
Do not make colour do all the work
An error state should not rely on red alone. A chart should not need perfect colour vision to understand. Add labels, icons, patterns, position and clear language. This usually makes the product easier for everyone, not only people using assistive technology.
Personality lives in the whole system, not in one low-contrast button.
Test it in context
Check the contrast ratio. Then look at the interface on a bright phone screen, in dark mode and at the size people actually read. Accessibility belongs in the component library from the first pass, not in a red-pen review before launch.
