react-doctor/no-gray-on-colored-background
Use a darker shade of the background color for text, or white/near-white for contrast. Gray text on colored backgrounds looks washed out
- Status
- Active
- Category
- Accessibility
- Assessment
- Evidence-required risk
- Required evidence
- source code, rendered UI, accessibility audit
- Default configuration
- Disabled until configured
- Default severity
- warn
Show technical metadata
- Scope
- All supported frameworks
- Active when
- always
- Requirements
- tailwind
- Tags
- design, test-noise
- Priority
- 33 (P3)
- Source
- oxlint-plugin-react-doctor
- Rule set
- oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
Validation prompt
Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.
Fires when className contains a gray-family text utility (text-gray|slate|zinc|neutral|stone-NNN) and a chromatic background utility such as bg-blue-500. This is a color-family heuristic, not a contrast calculation: it cannot resolve theme variants, opacity, gradients, inherited colors, overlays, or the final computed foreground and background. Pale tints with dark neutral text can already pass, so measure the rendered contrast before changing tokens.
Evidence boundary
The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.
Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.
The design tag controls activation and discovery. It does not determine the rule’s proof class.
Record one outcome:
- Confirmed failure: The required evidence establishes the violation.
- Rejected: A documented exception or false-positive predicate applies.
- Needs evidence: Named evidence can still be collected.
- Unavailable: Required evidence cannot be collected in this run.
- Waived with evidence: An authorized, scoped exception applies to an established failure.
- Observation: The review records an optional tradeoff without claiming a defect.
A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.
Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.
Fix prompt
Apply this candidate correction only after the required evidence confirms the risk.
Choose foreground and background tokens that fit the existing theme, then verify their rendered contrast: at least 4.5:1 for normal text, or 3:1 only for large-scale text (at least 24 CSS px regular or 18.66 CSS px bold). Include opacity, overlays, gradients, and interaction/theme states in the measurement; do not switch mechanically to white or a same-hue token without checking the result. See https://webaim.org/articles/contrast/
Repository-wide copy prompt
Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.
Show repository-wide prompt
Fix every confirmed react-doctor/no-gray-on-colored-background diagnostic in the current repository.
Required change:
- Choose foreground and background tokens that fit the existing theme, then verify their rendered contrast: at least 4.5:1 for normal text, or 3:1 only for large-scale text (at least 24 CSS px regular or 18.66 CSS px bold). Include opacity, overlays, gradients, and interaction/theme states in the measurement; do not switch mechanically to white or a same-hue token without checking the result. See https://webaim.org/articles/contrast/.
Validation before editing:
Fires when className contains a gray-family text utility (text-gray|slate|zinc|neutral|stone-NNN) and a chromatic background utility such as bg-blue-500. This is a color-family heuristic, not a contrast calculation: it cannot resolve theme variants, opacity, gradients, inherited colors, overlays, or the final computed foreground and background. Pale tints with dark neutral text can already pass, so measure the rendered contrast before changing tokens.
Constraints:
- Make the smallest change that fixes the root cause.
- Preserve behavior and interfaces unrelated to this diagnostic.
- Reuse existing project components, utilities, and conventions.
- Preserve accessible names, focus order, keyboard behavior, and touch access not targeted by this rule.
- Adapt identifiers and framework details instead of copying blindly.
- Do not disable the rule or suppress matching code.
Assessment:
- Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
- Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
- A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.
Verification:
- Run focused tests for the changed behavior.
- Run React Doctor and confirm this diagnostic no longer appears from changed code.
- Run an unfiltered scan of the affected scope before claiming no cross-category regression.
- Report the files changed and any checks you could not run.