Skip to content

Conversation

ludvigz
Copy link
Member

@ludvigz ludvigz commented Nov 13, 2026

Purpose

Several text colors in the PC builder's compatibility panel did not meet the WCAG AA contrast ratio of 4.5:1 on the bg-surface background (#485458): red-500 (2.05:1), orange-500 (2.79:1) and text-secondary (3.62:1). The yellow and green status colors also fell short (4.10:1 and 3.53:1). This PR raises them to at least 4.5:1 while keeping the existing design.

Changes

  • Add four status color tokens to colors.css (status-incompatible, status-warning, status-unknown, status-compatible) and use them in the compatibility panel instead of Tailwind's red/orange/yellow/green 500. The four colors share the same lightness and saturation, so they look like one set, and each is at least 4.5:1 on both the surface and background colors.

Contrast on #485458: incompatible 2.05 → 4.72, warning 2.71 → 4.97, unknown 4.10 → 5.13, compatible 3.53 → 5.31, secondary 3.62 → 4.70.

Related issues

Closes #90

Verification

Automated checks, run from frontend:

  • npx vitest run all tests pass

Screenshots

image image

@ludvigz ludvigz requested a review from a team as a code owner November 13, 2026 18:00
@ludvigz ludvigz linked an issue Nov 13, 2026 that may be closed by this pull request
5 tasks
@ludvigz ludvigz self-assigned this Nov 13, 2026
Copy link
Member

@oscarog oscarog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very good!

@oscarog oscarog merged commit 7944837 into dev Nov 13, 2026
@oscarog oscarog deleted the 90-improve-text-contrast-in-compatibility-panel branch November 13, 2026 22:09
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve text contrast in compatibility panel
2 participants