Problem
Lack of an established color system negatively affects the monitoring system and the brand overall:

• Zabbix has 299 hard-coded colors without a shared source of truth for what colors mean or how/when/where to use each color, so developers/designers aren't confident about which one to use and when
• None of the four themes meet WCAG color contrast requirements http://example.com; only 68% of the UI meets basic accessibility standards, just 48% in dark mode. This is a Level AA conformance failure, the level we need to achieve to meet
  European Accessibility Act (EAA) requirements.
• For example, 104 grayscale colors exist, and most are nearly identical. As a result, the same contrast failures keep appearing across components. By implementing a color system, the number of grayscale colors could be reduced to 11 and fix contrast issues by using ramp symmetry
• Every Zabbix product has its own colors; there is no color consistency across the ecosystem. This weakens the brand and dilutes user/customer trust

Solution:

• Establish color system foundation. OKLCH-based color ramps (perceptually consistent lightness/contrast across all hues); establish primitive layer tokens
• Audit and categorize legacy colors by their usage and appearance; define replacement values; evaluate color contrast of new values
• Assign color roles; establish 2nd-level semantic color tokens
• Gradually deprecate legacy colors and replace with new token values
• Create color system documentation for shared usage