XBlockStatus small status text uses a default color role below 4.5:1 on the light card

Open Beginner friendly
#3,282 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@nisatsama is already working on this.

Since Oct 2, 2026.

  • #3287 by @nisatsama — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript

Research direction

Start at src/course-outline/xblock-status/XBlockStatus.tsx around line 49 and inspect how the release/grading status line selects its text color and size. Reproduce a course outline with status data in the default light theme, measure the computed text/background contrast, and compare the result after using an appropriate body-text role. Done means ordinary small status text reaches 4.5:1 in the supported light and dark themes.

Written by the indexing model from the issue text.

Description

Checked 2026-09-30: master source at 3bf892bb1393fc2dd9ff37b2250c3a81281ab7e9 and release/verawood 3287ca73efaf9016a0da241462604dbd9b1a5346. Current source findings and older UI observations are distinguished below; no new upstream-browser or build acceptance is claimed.

XBlockStatus uses text-secondary-400 together with x-small for the release/grading status line. In the unpatched Verawood UI with Paragon 23.20.3 defaults, this was 12px #747474 text on a #F8F7F6 card, approximately 4.37:1. This is ordinary informative text; it is not a disabled-control case. The source still chooses that role at both current refs.

Reproduction: load a course outline with actual status data using the default light theme; inspect the status line's computed text/background colors and font size, and calculate their WCAG relative-luminance contrast. Run the same check after changing to an appropriate body-text color role.

Expected: ordinary small status text meets 4.5:1 in the supported light/dark themes. The exact historical colors/ratio above are not asserted for custom themes or a newly rendered master build; current browser remeasurement remains required. A downstream text-gray-700 change removed the historical default-theme failure, but a token that meets the intended semantic role in all supported themes is preferable.

Duplicate checks: current issue/PR search for XBlockStatus contrast and text-secondary-400 contrast returned no matching report.

Dominant language
TypeScript
Stars
18
Forks
228
Avg merge
2d 5h
Merged PRs (30d)
24

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openedx/frontend-app-authoring

All issues in openedx/frontend-app-authoring

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.