react-doctor/no-low-contrast-inline-style
Low-contrast text in inline style
- Category: Accessibility
- Severity: warn
- Source:
oxlint-plugin-react-doctor - Framework: global
- Enabled when: always
- Tags: design, test-noise
- Default: Disabled until configured
Validate the diagnostic
Confirm the reported code matches this rule before you edit it.
Confirm the reported code matches react-doctor/no-low-contrast-inline-style. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.
Compare the code
The corrected pattern shows a focused way to address the diagnostic.
Reported pattern
<p style={{ color: "#aaaaaa", backgroundColor: "#ffffff" }}>Status</p>Corrected pattern
<p style={{ color: "#595959", backgroundColor: "#ffffff" }}>
Status
</p>How to fix
Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.
Copyable fix prompt
Copy this self-contained prompt into your coding agent after you confirm the diagnostic.
Fix every confirmed
Reference transformation:Before:react-doctor/no-low-contrast-inline-style diagnostic in the current repository.
Required change:
- Text needs a WCAG contrast ratio of at least 4.5:1 (3:1 for large/bold text) against its background. Darken or lighten one of the colors until it passes.<p style={{ color: "#aaaaaa", backgroundColor: "#ffffff" }}>Status</p><p style={{ color: "#595959", backgroundColor: "#ffffff" }}>
Status
</p>Constraints:
- Confirm the reported code matches the Before pattern.
- Make the smallest change that fixes the root cause.
- Preserve behavior and interfaces unrelated to this diagnostic.
- Reuse existing project components, utilities, and conventions.
- Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
- Use existing brand assets, product facts, content, and design tokens.
- Do not invent claims, customer data, typefaces, or artwork.
- 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.
Verification:
- Run focused tests for the changed behavior.
- Run React Doctor and confirm this diagnostic no longer appears.
- Report the files changed and any checks you could not run.
Related rules
More Accessibility rules from the rules reference:
react-doctor/no-multiple-main-landmarks: View contains multiple main landmarksreact-doctor/no-multiple-unlabeled-navigation-landmarks: Repeated navigation landmarks need unique namesreact-doctor/no-noninteractive-element-interactions: Move the interaction to a semantic interactive element, or add an interactive role plus keyboard support.react-doctor/no-noninteractive-element-to-interactive-role: Use a semantic interactive element instead of role-promoting a non-interactive one.react-doctor/no-noninteractive-tabindex: Reserve tabIndex for interactive elements or interactive roles; remove it from non-interactive ones.