Use color intentionally. It’s not decoration. Color is supposed to be functional.
We have different shades for every defined color in Orbit. For most of our colors*, the following points should apply:
Every color has specific guidelines for meaning. We honor these guidelines in order to maintain consistency across the product.
It’s usually safe to combineLight and Dark shades of any color. Text in Dark shade should be readable on a Light shade background of its related color.
Dark shade of any color shouldn’t be used as a background.
Every non-dark color has two additional shades defined – :active and :hover. These additional shades should only be used for very specific cases.
All of our colors are also defined as design tokens, so non-Orbit components can use Orbit colors directly and they don’t need to define colors again in their local codebase.
*Colors in the Shades category are an exception because shades are usually used for general use cases like texts, headings, and borders.
Background & Foreground colors
We use two main colors for backgrounds:
Cloud / Light
And four colors to create status backgrounds:
Blue / Light
Green / Light
Orange / Light
Red / Light
These are used most of the time for backgrounds for any elevation level or component. These colors are accessible with dark foreground colors, so we recommended using Light shadesfor backgrounds and Dark shades for foregrounds. You can also use complementary and minor colors from our palette, which should help you have enough colors to work with.
Interactive colors are used in components with some indication of the state that do not move you forward in the flow or redirect you to another page. All of these elements should be colored in $$paletteBlue. The majority of these interactive elements cover hover, focus, select, active, press, and drag states.
Actionable colors are used in components that include an action (such as moving you forward in the flow). That means the Button, ButtonLink, and TextLink components. For the actionable color, we are use our main Product / Normal. Elements that are not actionable should not be in this color.
The color palette contains every one of the colors we use in our designs. These colors are also used by default in white label solutions for our partners and can be modified to their brand colors.
The reasoning behind additional color shades As you could notice, our basic color palette is quite simple – just a few shades.
However, for some specific interaction states and other visual perks, we defined additional color shades. It’s recommended to try design without using these shades, but when you feel you need to nudge some color a bit, additional color shades should help you.
rgb(236, 248, 247)
Product Light :hover
rgb(214, 240, 238)
Product Light :active
rgb(192, 232, 228)
rgb(0, 169, 145)
Product Normal :hover
rgb(0, 152, 130)
Product Normal :active
rgb(0, 143, 123)
rgb(0, 127, 109)
Product Dark :hover
rgb(0, 112, 96)
Product Dark :active
rgb(0, 102, 87)
rgb(0, 92, 78)
We are aware of a slight contrast issue with Kiwi.com’s Product Normal color and the issues when using it for Primary Buttons. We are exploring possible solutions.
We highly recommend against using it for text and we recommend using darker shades, if possible.
It can interfere with the visual priorities on the page and draw attention to non-action elements. Generally, buttons should be the only elements with dark backgrounds. Nothing on the page should draw attention away from them.
We try to keep our UI light as possible, so we use only Cloud colors or Light shades for backgrounds.
rgb(255, 255, 255)
rgb(245, 247, 249)
rgb(229, 234, 239)
Use White as background color for content sections
It allows important information to appear on the page without interference.