`react-doctor/radio-input-missing-name`

Radio input missing name

Category: Accessibility
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: always
Default: Enabled

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/radio-input-missing-name. 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

<><input type="radio" value="monthly" /><input type="radio" value="yearly" /></>

Corrected pattern

<>
  <input type="radio" name="billing" value="monthly" />
  <input type="radio" name="billing" value="yearly" />
</>;

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/radio-input-missing-name diagnostic in the current repository. Required change: - Give every radio in the same group the same name prop (e.g. <input type="radio" name="shippingSpeed" />). The browser groups radios and enables arrow-key navigation only when they share a name.

Reference transformation:Before:

<><input type="radio" value="monthly" /><input type="radio" value="yearly" /></>

After:

<>
  <input type="radio" name="billing" value="monthly" />
  <input type="radio" name="billing" value="yearly" />
</>;

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. - 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.

More Accessibility rules from the rules reference:

react-doctor/require-reduced-motion: Project ships a motion library but never gates animation on the user's reduced-motion preference — add `useReducedMotion()` / `<MotionConfig reducedMotion="user">` or a `@media (prefers-reduced-motion: reduce)` query
react-doctor/role-button-requires-complete-keyboard-activation: ARIA button handles only one activation key
react-doctor/role-has-required-aria-props: Require elements with an ARIA role to carry that role's required aria-* state props, like aria-checked on role='checkbox'.
react-doctor/role-supports-aria-props: Use only aria-* props that are supported by the element's explicit or implicit ARIA role.
react-doctor/scope: Disallow the scope attribute on elements other than th — it is only defined for table header cells.

react-doctor/radio-input-missing-name