As identified by cafuego on JENKINS-65124, Jenkins build status symbols suffer from Accessibility issues for those users with color-blindness. Specifically, the new build status symbols introduced in PR # 5065 are not distinguishable for color-blind users.
(I am not a UI/UX expert and not not have a color-blindness condition; just raising the issue)

The issue may extend across other features where red/green/yellow is used to distinguish categories (eg: Pipeline Stage View Plugin, plugins using eCharts-API, warnings-ng-plugin, Job Configuration History, Test Results Analyzer and more.

Recommendation to convert this to its EPIC and separate create issues for known plugins with issues, as done for tables-to-divs issue.

However, before addressing any specific issues, a review of and a recommendation on "standard colors" and style guide be developed such that plugin developers can reference standardized css class color library with defined colors (eg: class="color-warning"),

Background information on the color problem can be found here.
Color blindness: how to design an accessible user interface
DEFECTIVE COLOR VISION AND TRAFFIC SIGNALS
Color Blindness & Web Design

Users who have color-blindness conditions or UI/UX experts may wish to be engaged/provide feedback.

A recommendation may be to embed information symbols or patterns in an alternate shade as suggested in the traffic lights and as seen in the Mozilla browser compatibility chart.

Additional information is available from work SonarQube performed on the issue:
Concerning the usage of colors, Accessibility issues, SONAR-11959: Colorblind-friendly coverage treemaps.

Unrelated Jenkins instance feedback on color.