Yevgeniy Belov

Reducing color decisions while improving consistency and accessibility

As CloudGuard grew, every new component added color choices to make and check. I redesigned the color system to reduce the decisions designers needed to make, improve visual consistency, and reduce accessibility risks across colors and themes.

Manual color mappings in this illustration —
Role
Product Designer
Tools
Figma variables and modes
Scope
DS in Figma
Timeline
1 month · 2025
Summary

Summary

Problem

Every component tuned its colors separately for each hue, theme, and state. Similar levels looked inconsistent across hues, and some valid token pairs failed contrast.

Constraints

The brand palette had to stay as it was.

Solution

Two new token layers on top of the palette: strength (lightness) and hue, plus saturation and inverse modes. Components own only a contrast recipe.

Impact
87.5% fewer manual color mappings per element in core components with color variants
3 → 0 hue families with contrast failures across components on main backgrounds in regular mode
Context

Context

CloudGuard helps customers protect thousands of cloud resources. Teams decide what needs attention using three signals: business priority, risk score and vulnerability severity. Each has its own color scale, so statuses are easy to tell apart.

Business priority

How important the asset is to the customer.

  • Crown Jewel
  • High Importance
  • Important
  • Low Importance

Severity

How serious the vulnerabilities affecting the asset are.

  • Critical
  • High
  • Medium
  • Low
  • Info

Risk

Assessment of the asset’s exposure.

  • Critical
  • High
  • Medium
  • Low
Problem

Problem

As the design system grew, more colorful components were added, and every one of them repeated the same color work.

For example, the Score Tile component needed 320 color mappings: five elements across four UI states, two inverse modes and eight hues. Each new variant multiplied the color choices to make and check.

Reframing the problem

How can we reduce the amount of design decisions and contrast issues?

Constraints

Constraints

The palette had to stay. It defined the brand colors and was already used across the product. My scope was the layer between the palette and the components: how components choose colors, not which colors exist.

Exploration

Exploration

Many CloudGuard components needed the same color hierarchy across several hues and both themes. With the palette fixed, I considered three ways to reduce the mapping work repeated across components.

Direction A Direct mapping

Use palette colors directly.

B Component tokens

Give each element its own token.

C Chosen Strength mapping

Use strengths; resolve colors centrally.

Color token exampleR-20score-tile-bg-danger-defaultbg-weakest
Avoids repeated mapping work No: The same palette choices are made in every component No: The same relationships are redefined for each component token Yes: Relationships are defined once and reused
Consistent across components No: Each component makes its own choices Partly: Tokens are stable, but not shared across components Yes: Components share one hierarchy
Adapts to themes and contexts No: Every mapping is revisited Partly: Each token gets a value per theme Yes: Resolved centrally for hue, saturation and theme
Stable design–development contract No: Components reference palette colors directly Yes: Components reference their own tokens Yes: Components reference roles and strengths
Full local control Yes: Any element can use any color Yes: Each element has its own token Partly: Through overrides, which weaken consistency if overused
Quick to set up Yes: Nothing to set up Partly: A token for every element No: Rules to build and validate
Changes stay isolated Yes: One component at a time Yes: One token at a time No: Shared changes need calibration across components
DecisionIt kept every color decision local, so the same mapping work and consistency checks would keep repeating as the system grew.It gave each element a stable contract, but repeated the same color relationships across a growing set of component tokens.It let components reuse one hierarchy across contexts and themes. I accepted the initial complexity and broader validation needed for shared changes.
Solution

Solution

I built shared foreground and background strength levels on top of the existing palette. Components use them to set emphasis, rather than choosing a separate color for every variant.

Figma modes control hue, saturation and inverse independently. Each component owns one contrast recipe, and the system maps it to palette colors across every combination and both themes.

Strength levels

Use shared foreground and background levels to express emphasis, independent of hue and theme.

Hue modes

Map the same strength levels across hues so changing color preserves the component’s hierarchy.

Saturated mode

Make text and icons more vivid when color helps distinguish meanings, such as severity levels.

Inverse mode

Flip colors relative to the current theme so highlighted components stand out in both light and dark.

Result

Result

What designers do

In Figma, designers switch hue, saturation or inverse mode on a single Score Tile. The shared mappings update its colors and keep the same strength recipe, with no tuning per variant.

What users see

Risk, priority and severity share the same color relationships across the screen.

CloudGuard entity details showing risk findings, business priority, and a context graph in consistent colors
Validation

Validation

I checked every foreground and background pair against WCAG AA at eight text sizes. The check covered 192 combinations of hue, theme, saturation, inverse mode, and main background.

In regular mode, every pair on the three main backgrounds passes. Other modes still have failures:

  • Extra backgrounds: 5 of 8 hues in light theme, all 8 in dark.
  • Inverse, on main backgrounds: all 8 hues in light theme, 5 of 8 in dark.
  • Saturated: the most failures, especially combined with inverse.

The check below runs live on the real tokens: change any mode and every ratio is measured again.

Theme
Saturation
Inverse
Neutral · 1 of 8

Neutral

Main BG strengthsChecking…
Extra BG strengthsChecking…
BG weak
FG strong
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
FG regular
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
FG weak
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
BG regular
FG strong
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
FG regular
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
FG weak
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
BG strong
FG strong
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
FG regular
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
FG weak
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
BG stronger
FG strong
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
FG regular
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
FG weak
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
BG strongest
FG strong
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
FG regular
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
FG weak
A xs
A md
A lg
A xl
A 2xl
A 3xl
A 4xl
A 5xl
Impact

Impact

87.5% fewer manual color mappings. In core components with color variants, designers went from assigning eight colors per element, one for each hue, to defining one mapping shared across all eight hues. That keeps the same visual hierarchy across hues.

Zero contrast issues on the three main backgrounds in regular mode. Yellow, orange, and green variants previously had contrast issues across components. The new system passes these checks in both themes. Remaining issues in saturated and inverse modes and on extra backgrounds can now be checked and fixed centrally.

Next case study

Designing a conversation-first interface

I designed how customers move between a conversation and its artifacts in a Check Point interface.

Read nextor press →