Our color palette is built with our core principles and guidelines as its foundation. We are committed to complying with WCAG 2.1 AA standard contrast ratios.
- Use official color palette colors and variables for all color CSS declarations. Never hard-code a color without a variable.
- Use rgba() to add transparency when the color needs to blend with different backgrounds.
White is used for text and icons on dark backgrounds.
Gray 100 is the product’s canvas. Gray 200 is for hover states or headers of expanded content. Gray 300 for most other gray elements like tags, avatars, disabled inputs. Gray 400 is not currently used. Gray 500-600 are primarily used for borders and dividers.
Purple 800 is our default text color, Purple 600 is used for our Default header color. Purple 500 → Purple 100 can be used for Prominent moods.
Used for semantic text (links), secondary actions and general informative moods including guidance and onboarding.
Used for reversed Primary actions on our Default Header and general positive moods (E.g. success messages, status, progress).
Used for highlighting Collective Intelligence assets and cautionary moods (e.g. warning messages, progress).
Used for indivating assertive moods, (E.g. action empty states, assertive confirmation modal).
Used for destructive actions and negative moods (e.g. error messages, status, progress).
To learn more, Culture Amp employees can visit the Color page in Figma.
- Contrast and accessibility is crucial. To consider everyone, we use color contrast ratios that adhered to WCAG 2.1 AA guidelines.
- Use our official color palette variables for all color CSS declarations.
rgba()to add transparency to a color, e.g.
- Please avoid using the deprecated custom helper
add-alpha(), as it requires importing a deprecated module and will not break the build when it is missing.
- Be mindful of color psychology associations and cultural values (such as red symbolizing danger versus good luck).
To indicate links and on-page actions, use Blue 500.
For the most important action on a page, use Blue 500 or Green 400 as the Primary button color on our Default Header (Purple 600 background).
See data visualization for details.
- For favorable scores and general positive colored graphs and visualizations, use Data Viz / Favorable
- For unfavorable scores and general negative colored graphs and visualizations, use Data Viz / Unfavorable
- Colors can help to create visual patterns that the user can recall (for example, links are always Blue colored or negative favorability scores, errors, and destructive actions are always Red).
- Use colors to create visual hierarchy.
- Colors can help to determine the level of severity.
- Add tone and contrast to define areas and guide or call out certain information.
- Use color for aesthetics or visual stimulation when it adds value to the page.
- Use more than color alone to convey information. Test with with a gray scale filter and color blindness simulators.
- Avoid using color when you can use contrast (such as levels of Purple or Neutrals), spacing, or typography to create hierarchy or groupings.
- Avoid color when there’s a risk of overuse or a ‘candy shop’ effect.
- Avoid color when it might overload the user and create confusion.
Here are some examples of existing design system colors: