New
Introducing React Bench, see how different models perform on React code
Menu
What Is React Doctor?
Quickstart
Install for Coding Agents
How to Fix Issues
GitHub Actions Setup
Updating CI
Other CI Providers
Migrating to CI v2
Config Files
ESLint & oxlint Plugins
Add Custom Rules
CLI Reference
GitHub Action Reference
Node.js API
Changelog
Modified MIT License
Terms of Service
Privacy Policy
Data Use
Security
Support
Rules reference

react-doctor/no-arbitrary-px-font-size

Pixel arbitrary font size

  • Category: Accessibility
  • Severity: warn
  • Source: oxlint-plugin-react-doctor
  • Framework: global
  • Enabled when: tailwind
  • 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-arbitrary-px-font-size. 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 className="text-[13px]">Last updated today</p>

Corrected pattern

<p className="text-sm">Last updated today</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 react-doctor/no-arbitrary-px-font-size diagnostic in the current repository. Required change: - Use rem for arbitrary font sizes (text-[0.8125rem], not text-[13px]) so text scales with the user's root font-size preference. Pixels stay fine for border-* / outline-*.
Reference transformation:Before:
<p className="text-[13px]">Last updated today</p>
After:
<p className="text-sm">Last updated today</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. - Confirm this rule is enabled for the project: tailwind. 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.

More Accessibility rules from the rules reference: