Skip to content

fix(a11y): fix contrast of event meta-text in Events tab (CRW-10318)#1591

Open
olexii4 wants to merge 1 commit into
mainfrom
CRW-10318
Open

fix(a11y): fix contrast of event meta-text in Events tab (CRW-10318)#1591
olexii4 wants to merge 1 commit into
mainfrom
CRW-10318

Conversation

@olexii4
Copy link
Copy Markdown
Contributor

@olexii4 olexii4 commented May 28, 2026

What does this PR do?

Fixes a WCAG 1.4.3 Contrast (Minimum, Level AA) violation in the Events tab on both the Workspace Details page and the Start Workspace progress page.

Fix

One CSS custom property override in WorkspaceEvents/Item/index.module.css:

.header {
  --pf-v6-c-content--small--Color: var(--pf-t--global--text--color--regular);
}

No HTML structure changes — the fix is CSS-only and scoped to the event card header.


Screenshot/screencast of this PR

After: meta text at ≥ 4.5:1 — no contrast violation.
Знімок екрана 2026-05-28 о 03 45 41


What issues does this PR fix or reference?

fixes https://redhat.atlassian.net/browse/CRW-10318

Is it tested? How?

Release Notes

Docs PR

The gray meta-information text in each event card (involved object name
and 'Generated from <source>' line) used PatternFly's subtle text color
token (--pf-t--global--text--color--subtle), which produces a contrast
ratio of ~3.65:1 against the card background. This fails WCAG 1.4.3
Contrast (Minimum, Level AA), which requires 4.5:1 for standard text.

Override --pf-v6-c-content--small--Color at the CardHeader container
level to use --pf-t--global--text--color--regular, which achieves a
contrast ratio of at least 4.5:1.

Affected pages: Workspace Details > Events tab,
                Start Workspace progress > Events tab.

Signed-off-by: Oleksii Orel <oorel@redhat.com>
@olexii4 olexii4 requested review from artaleks9 and svor May 28, 2026 00:41
@olexii4 olexii4 requested review from akurinnoy and ibuziuk as code owners May 28, 2026 00:41
@che-bot
Copy link
Copy Markdown
Contributor

che-bot commented May 28, 2026

Click here to review and test in web IDE: Contribute

@github-actions
Copy link
Copy Markdown

Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1591 (linux/amd64, linux/arm64)

kubectl patch command
kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1591", name: che-dashboard}]}}]"

@olexii4 olexii4 requested review from dmytro-ndp and removed request for artaleks9 May 28, 2026 01:05
@codecov
Copy link
Copy Markdown

codecov Bot commented May 28, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.49%. Comparing base (f87012b) to head (7a55382).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1591   +/-   ##
=======================================
  Coverage   92.49%   92.49%           
=======================================
  Files         563      563           
  Lines       56254    56254           
  Branches     4267     4267           
=======================================
  Hits        52030    52030           
  Misses       4174     4174           
  Partials       50       50           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown
Contributor

@svor svor left a comment

Choose a reason for hiding this comment

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

lgtm

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 28, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: olexii4, svor

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants