`react-doctor/fieldset-requires-legend`

Fieldset group has no legend

Category: Accessibility
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: react
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/fieldset-requires-legend. 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

const Contact = () => (
  <fieldset>
    <label>
      Email
      <input />
    </label>
    <label>
      Phone
      <input />
    </label>
  </fieldset>
);

Corrected pattern

const Contact = () => (
  <fieldset>
    <legend>Contact method</legend>
    <label>
      Email
      <input />
    </label>
    <label>
      Phone
      <input />
    </label>
  </fieldset>
);

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/fieldset-requires-legend diagnostic in the current repository. Required change: - Name grouped controls with a direct legend, or an explicit accessible name when no visible group label is appropriate.

Reference transformation:Before:

const Contact = () => (
  <fieldset>
    <label>
      Email
      <input />
    </label>
    <label>
      Phone
      <input />
    </label>
  </fieldset>
);

After:

const Contact = () => (
  <fieldset>
    <legend>Contact method</legend>
    <label>
      Email
      <input />
    </label>
    <label>
      Phone
      <input />
    </label>
  </fieldset>
);

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. - Confirm this rule is enabled for the project: react. 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/heading-has-content: Disallow empty headings — h1 through h6 must render accessible text content.
react-doctor/html-has-lang: Require a lang attribute on the html element so screen readers use the right pronunciation rules.
react-doctor/html-no-nested-interactive: Hoist the inner interactive element out, or make the outer one a non-interactive wrapper: change <a><a/></a> to <a/> next to <a/>, or wrap with <div>/<span>
react-doctor/html-xml-lang-mismatch: Conflicting document language declarations
react-doctor/iframe-has-title: Require a unique, descriptive title attribute on iframes so assistive-tech users can identify embedded content.

react-doctor/fieldset-requires-legend