Accessible website color palettes

An accessible website color palette is one where every text and background pair reaches the WCAG contrast minimum: 4.5:1 for normal text and 3:1 for large text at level AA. Start by checking the pairs you actually use, then fix any that fail before you export the palette to CSS.

This page maps the full workflow to the free tools that do each step: test one pair, test a whole palette, fix a failing pair, generate a palette from a brand color or image, and export the result as CSS.

The accessible color workflow

Work through the steps in order, or jump straight to the one you need. Each tool runs in your browser and gives you a value you can copy into your design system.

  1. Step 1

    Check one text and background pair

    Enter the foreground and background HEX values to see the contrast ratio and whether the pair passes WCAG AA or AAA for normal and large text.

    Result: A ratio, an AA/AAA pass or fail result and copy-ready color values for one pair.

  2. Step 2

    Check a full palette

    Paste up to six colors from your design system and the checker tests every text and background combination, so you can see which pairs are readable before you build components.

    Result: A pass or fail result for every pair in the palette, with the ratio for each.

  3. Step 3

    Fix a failing pair

    When a pair misses AA, pick the text size and level you need, then adjust the text or background color until the ratio clears the threshold.

    Result: A corrected HEX or CSS value that passes the level you chose.

  4. Step 4

    Generate an accessible palette

    Start from one brand HEX and get background, surface, text, primary and accent roles, each with a WCAG AA result against the background it sits on.

    Result: A role-based palette you can copy as HEX or CSS variables.

  5. Step 5

    Start from an image or logo

    Extract 5–8 dominant colors from a logo, photo or moodboard, then test the resulting palette for contrast before you commit to it.

    Result: A small HEX palette extracted in the browser, ready to copy or refine.

  6. Step 6

    Export the palette as CSS

    Turn one brand color into a full 50–950 scale and copy it as CSS variables, a Tailwind v3 config or a v4 @theme block.

    Result: Shade scales and CSS-ready token values for your stylesheet or Tailwind theme.

Which tool do I need?

Match your task to the tool. Each row names the job, the tool that does it and the result you get.

TaskToolWhat you get
Test one pairContrast checkerRatio and AA/AAA result for one foreground and background
Test every pairPalette accessibility checkerPass or fail for up to 15 pairs from six colors
Fix a failurePalette contrast fixerAdjusted colors that meet the level you choose
Build a paletteAccessible palette generatorRole-based palette with WCAG results
Export for codeTailwind color generator50–950 scale as CSS variables or Tailwind theme values

Fix the pair, not the whole palette

A palette usually fails on one or two combinations, not all of them. Identify the failing pair with the palette accessibility checker, then open the palette contrast fixer and adjust only the text or background value. Keep brand colors where you can and darken or lighten the neutral around them; a small shift in a grey often clears 4.5:1 without changing the look of the brand.

If you are starting from scratch instead, the accessible color palette generator builds role-based colors from one brand HEX, and the image to palette extractor pulls a starting palette out of a logo or screenshot. Once the colors pass, export them with the Tailwind color generator or browse the wider free design tools.

Learn from palettes that already pass

Seeing real combinations helps you judge a ratio. Browse accessible website color palettes with measured contrast ratios, or the wider website color scheme library to compare palettes by hue.

WCAG text contrast thresholds

Text sizeAAAAA
Normal text4.5:17:1
Large text3:14.5:1

Accessible color palettes — FAQ

What is an accessible color palette?

An accessible color palette is a set of colors where every text and background combination people actually use reaches the WCAG contrast minimum: 4.5:1 for normal text and 3:1 for large text at level AA. A palette is only accessible where those pairs are used that way, so the same two colors can pass for a heading and fail for small body copy.

What contrast ratio do WCAG AA and AAA require?

WCAG 2.2 level AA requires at least 4.5:1 for normal text and 3:1 for large text. Level AAA raises those to 7:1 and 4.5:1. Large text means at least 18pt regular or 14pt bold, which is roughly 24px and 18.66px in CSS.

How many colors should an accessible palette have?

Most interfaces work with five roles: a background, a surface for cards, a text color, a primary action color and one accent. That keeps the number of pairs you must test small enough to check every one. Add semantic colors for success, warning and error only when you need them, and test each against its own background.

Does passing contrast make my site accessible?

No. Contrast is one WCAG requirement. Keyboard access, visible focus states, alternative text, heading order, form labels, text over images and hover and disabled states all need their own checks. Use these tools to settle the color pairs, then audit the rest of the interface separately.

Do these tools upload my colors or images?

No. Every tool on this page runs in your browser, so the HEX values and images you enter stay on your device. There is no sign-up and nothing to install.