New
Introducing React Bench, see how different models perform on React code

react-doctor/no-tiny-text

Use at least 12px for body content, 16px is ideal. Small text is hard to read, especially on high-DPI mobile screens

Status
Active
Category
Accessibility
Assessment
Evidence-required risk
Required evidence
source code, rendered UI, accessibility audit, product intent
Default configuration
Disabled until configured
Default severity
warn
Show technical metadata
Scope
All supported frameworks
Active when
always
Tags
design, test-noise
Priority
47 (P3)
Source
oxlint-plugin-react-doctor
Rule set
oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
On this page

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Confirm style.fontSize resolves to a pixel value below 12. The rule treats bare numbers as px, parses Npx directly, and converts Nrem assuming a 16px root. Footnotes, legal disclaimers, and dense tabular data near 11px are occasionally intentional but should still be reviewed for readability.

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.

Use at least 12px (0.75rem) for any body content; 16px (1rem) is ideal for prose. Captions and labels can go to 14px (0.875rem) with strong contrast. Don't shrink the font to make a layout fit: fix the layout. See https://www.w3.org/WAI/WCAG21/Understanding/visual-presentation

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-tiny-text diagnostic in the current repository.

Required change:

Validation before editing:

Confirm style.fontSize resolves to a pixel value below 12. The rule treats bare numbers as px, parses Npx directly, and converts Nrem assuming a 16px root. Footnotes, legal disclaimers, and dense tabular data near 11px are occasionally intentional but should still be reviewed for readability.

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.