react-doctor/no-transitioned-focus-ring

Keep focus indication immediate by removing only the transition that delays a ring or outline

Validation prompt

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

For react-doctor/no-transitioned-focus-ring, the detector reads a literal className containing a visible focus ring or outline. It reports that class with an unvarianted transition-shadow utility or a supported arbitrary transition naming shadow or outline. It does not inspect CSS modules, inline styles, dynamic classes, or every variant-scoped transition. Confirm the focus indicator is actually transitioned when keyboard focus arrives; do not infer a missing focus style from this diagnostic. The Before example is representative, not exhaustive.

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.

Review a candidate correction

Apply this candidate correction only after the required evidence confirms the risk.

Reported pattern

const Demo = () => (
  <button className="transition-shadow focus-visible:ring-2">Save</button>
);

Candidate corrected pattern

const Demo = () => (
  <button className="focus-visible:ring-2">Save</button>
);

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Remove or narrow only the transition that delays the focus ring or outline. Preserve the existing focus-visible utility, color, width, offset, contrast, border radius, and every unrelated hover or active transition. If the same transition utility serves other states, replace it with explicit non-focus properties rather than swapping the focus treatment to a different visual system. Verify keyboard focus appears immediately in every affected theme and forced-colors setting.

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.

const Demo = () => (
  <button className="transition-shadow focus-visible:ring-2">Save</button>
);

const Demo = () => (
  <button className="focus-visible:ring-2">Save</button>
);