Maturity
Overview
Color is a powerful tool for directing people’s attention, highlighting important information, and evoking emotions. Our eyes naturally gravitate towards it. We use it strategically to guide people and enhance their experience.
Having small touches of color makes it more colorful than having the whole thing in color.
— Dieter Rams
Related content
Our principles in practice
Our identity principles guide how we define our foundations to create a better experience for everyone. Here’s how they apply to color:
- Coherent: We have assigned specific semantic sentiments to colors to establish a coherent meaning throughout the experience, making it more predictable and easier to understand.
- Empowering: Color is a powerful tool for directing people’s attention, highlighting important information, and evoking emotions. Our eyes naturally gravitate towards it. We use it strategically to guide people and enhance their experience.
- Clear: Color is a crucial experience guiding element. We use it to highlight important elements, details, words, etc. Overusing color can distract people and defeat that purpose.
- Inclusive: Our color system provides a good contrast level in every context. Contrast defines how easily a person distinguishes one element from an adjacent one: higher contrast means higher visibility and legibility. Color contrast can be measured numerically using the standard defined in the WCAG 2.1 guidelines.
But using color alone to convey information can be exclusive for colorblind people—approximately 4.5% of the world. We reinforce the differences between elements using icons.
Further reading
Color scales
Each color has eight luminance steps, with two additional lighter and darker values for the Neutral. Each step was designed for at least one specific use case. Here’s a simplified overview:
Step |
Product use case |
Marketing use case |
---|---|---|
000 (Neutral only) |
App background onExtra content (Inverted) Primary content |
Main background |
100 |
Surface |
TBD |
200 |
Surface hovered |
Surface Light |
300 |
Surface pressed |
TBD |
400 |
(Inverted) Secondary content |
TBD |
500 |
Extra |
onSurface Light |
600 |
Extra hovered Secondary content |
TBD |
700 |
Extra pressed |
TBD |
800 |
(Inverted) App background |
Surface Dark |
900 (Neutral only) |
Primary content |
Primary content |
Core color palette
Core colors are the joint base for the App and Marketing. They have generic names and the full color scale. On top of this, we can use specific libraries that simplify their use for particular purposes—as in the App—which target these Core values.
Primary colors
Blue
Maze Blue is our primary color and represents an essential part of our brand personality. It plays a vital role in our designs, both in product and marketing.
Neutral
Neutral is the base color for content both in product and marketing.
Secondary colors
They are used as a complement, to differentiate and draw attention to specific elements, or as decoration, especially in marketing communications.
Accessible pairings
Quality checklist
This element passes the following requirements described in our Component lifecycle.
Maturity
α · Design tokens
It uses Ariane design tokens.
α · Official assets
It uses the official Ariane assets (e.g., icons and illustrations) in one of the official sizes.
α · Accessible use of color
Its color contrast ratio is at least 4.5:1 for text and interactive areas.
α · Target areas
Its interactive target areas are large enough for users to accurately select them, following the Fitts law.
α · Naming agreement
Its name is agreed upon and shared between design and development.
α · Responsive L1
Is responsive to different viewport sizes.
α · User-triggered states
If the component is interactive, all its possible user-triggered interactive states are defined.
β · Responsive L2
The responsive behavior has been reviewed and validated by the team.
β · State properties
All the possible state attributes are defined.
β · Docs L1
It has essential documentation with at least primary usage.
β · Use cases
All the uses are audited and refined.
RC · Definition agreement
Its naming and properties are audited and aligned in design and code.
RC · Accessible L1
Its accessibility is manually audited, and any significant issues are fixed.
RC · Docs L2
The documentation covers the most common use cases and is expected to be iterated during the Release Candidate phase.
RC · Storybook
Includes a Storybook playground of the component.
Stable · Stable API
The component and its API remain stable, with no breaking changes for at least one month.
Stable · Adaptive
Supports adaptive design via preference queries.
Stable · Docs L3
Detailed documentation exists for design, content, accessibility, and implementation, including do’s and dont’s.