Kerbly

Accessible lime color palette

Fresh and eye-catching, and a poor match for white text.

Your brand colour

Try an example

What your colour can do

#84cc16

Sits at step 400 of your scale

  • ✕ FailWhite text on your colour: 1.98:1. Too faint for normal text (needs 4.5:1).
  • ✓ PassBlack text on your colour: 10.63:1. Dark text works here.

Use black or very dark text on this colour, or step 600 (#518200) for white text. It keeps your hue and reaches 4.62:1.

Your colour scale

Eleven steps from very light to very dark, evenly spaced to the eye. Each tile shows the text colour that reads best on it.

  1. 50

    #effce4

    Black 19.71

  2. 100

    #ddf7c7

    Black 18.2

  3. 200

    #beec93

    Black 15.61

  4. 300

    #9cda59

    Black 12.59

  5. 400 (your colour)

    #84cc16

    Black 10.63

  6. 500

    #65a000

    Black 6.58

  7. 600

    #518200

    White 4.62

  8. 700

    #406800

    White 6.57

  9. 800

    #305000

    White 9.24

  10. 900

    #203800

    White 12.91

  11. 950

    #102000

    White 17.09

See the contrast numbers for every step
Contrast ratio of each step on white and on a dark background
StepColourOn whiteOn dark (#111111)
50#effce41.07:1 ✕17.73:1 ✓ AA
100#ddf7c71.15:1 ✕16.37:1 ✓ AA
200#beec931.35:1 ✕14.04:1 ✓ AA
300#9cda591.67:1 ✕11.32:1 ✓ AA
400 (yours)#84cc161.98:1 ✕9.56:1 ✓ AA
500#65a0003.19:1 large text only5.92:1 ✓ AA
600#5182004.62:1 ✓ AA4.08:1 large text only
700#4068006.57:1 ✓ AA2.88:1 ✕
800#3050009.24:1 ✓ AA2.04:1 ✕
900#20380012.91:1 ✓ AA1.46:1 ✕
950#10200017.09:1 ✓ AA1.1:1 ✕

Safe pairs to use

Picked from your scale so each one passes WCAG, with the ratio shown.

  • Book now

    Button with white text

    The lightest step that still gives white text 4.5:1.

    White on 6004.62:1 ✓ Pass

  • Read the details

    Links and text on white

    Coloured text on a white page needs 4.5:1 too.

    600 on white4.62:1 ✓ Pass

  • Read the details

    Links on a dark background

    For dark mode or dark sections. The darkest step that still reads on near-black.

    500 on dark5.92:1 ✓ Pass

  • Input with a border

    Borders, icons and focus rings

    Parts of controls need 3:1 against what they sit on (WCAG 1.4.11).

    500 on white3.19:1 ✓ Pass

  • Callout text

    Text on a light tint

    Callouts and badges: a very light background with a dark step for the text.

    950 on 5016.05:1 ✓ Pass

Take it with you

:root {
  --lime-50: #effce4;
  --lime-100: #ddf7c7;
  --lime-200: #beec93;
  --lime-300: #9cda59;
  --lime-400: #84cc16;
  --lime-500: #65a000;
  --lime-600: #518200;
  --lime-700: #406800;
  --lime-800: #305000;
  --lime-900: #203800;
  --lime-950: #102000;
}

The short answer

Lime (#84cc16) does not work with white text. The ratio is only 1.98:1, below the 4.5:1 needed for AA. Dark text works instead, at 10.63:1. If you want white text, use step 600 (#518200), which reaches 4.62:1.

Lime shades and their contrast

Lime scale with contrast ratios on white and on a dark background
StepColourOn whiteOn dark
50#effce41.07:1 ✕17.73:1 ✓ AA
100#ddf7c71.15:1 ✕16.37:1 ✓ AA
200#beec931.35:1 ✕14.04:1 ✓ AA
300#9cda591.67:1 ✕11.32:1 ✓ AA
400 (yours)#84cc161.98:1 ✕9.56:1 ✓ AA
500#65a0003.19:1 large only5.92:1 ✓ AA
600#5182004.62:1 ✓ AA4.08:1 large only
700#4068006.57:1 ✓ AA2.88:1 ✕
800#3050009.24:1 ✓ AA2.04:1 ✕
900#20380012.91:1 ✓ AA1.46:1 ✕
950#10200017.09:1 ✓ AA1.1:1 ✕

Questions about lime

Does lime work with white text?

Not at normal text sizes. Lime (#84cc16) has a contrast ratio of 1.98:1 with white, below the 4.5:1 WCAG AA asks for. The nearest shade that works is step 600 (#518200) at 4.62:1.

Does black text work on lime?

Yes. Black on #84cc16 is 10.63:1, which passes AA, so dark text is a good choice on this colour.

Which shade of lime should I use for links on a white page?

Use a step that reaches 4.5:1 on white. For lime that is step 600 (#518200), at 4.62:1.

Other colours

Build a scale from your own colour or check two colours.

Is your live site using these colours well?

A free scan checks every colour pair on your page against WCAG 2.2 and shows what to fix.

No account needed. Takes about 30 seconds.