AI called the palette accessible. Check the text against its background.

A pleasing set of colors is not a contrast test. Check each actual text-and-background pair and the states in which it appears.

Ask AI for exact foreground and background colors, then calculate their contrast rather than accepting “accessible” as a label. WCAG 2.2’s minimum contrast criterion generally requires 4.5:1 for ordinary text and 3:1 for large text, with specified exceptions.

An attractive gray can still be too faint

Using the W3C sRGB luminance formula, we calculated opaque #999999 text on #FFFFFF at about 2.85:1. It misses the 4.5:1 ordinary-text threshold. Changing the text to #595959 gives about 7.00:1 on the same background. These are local calculations for invented pairs, not a tested AI-generated design.

Ask for pairs, not just a palette

Suggested input: “List the exact text and background hex colors for body copy, links and error messages. Include hover and selected states. Do not claim a WCAG pass until each applicable pair is checked.” A list of five attractive colors does not say which ones will sit together.

Check the final rendering too

Our recommendation is to inspect the real page after calculating. Transparency, images and gradients can change the background behind text. Use the colors that actually appear, and check the relevant text size and state rather than transferring a result from a different pair.

Keep the claim narrow

Passing a text-contrast check does not establish that a whole product is accessible. Keyboard operation, meaningful labels and other requirements need their own checks. We have not audited a product or tested readers’ ability to use this palette.

Published October 14, 2026. Two opaque sRGB color pairs were calculated locally. No AI design tool, user study or full accessibility audit was performed; this guide is about text contrast, not legal certification.

Sources: W3C WAI · Contrast.