`react-doctor/no-aria-invalid-without-description`

Invalid control has no error description

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/no-aria-invalid-without-description. 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 EmailField = () => (
  <input aria-invalid type="email" />
);

Corrected pattern

const EmailField = () => (
  <>
    <input
      aria-invalid
      aria-describedby="email-error"
      type="email"
    />
    <p id="email-error">Enter a valid email address.</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-aria-invalid-without-description diagnostic in the current repository. Required change: - Connect an invalid control to its error text with aria-describedby or aria-errormessage.

Reference transformation:Before:

const EmailField = () => (
  <input aria-invalid type="email" />
);

After:

const EmailField = () => (
  <>
    <input
      aria-invalid
      aria-describedby="email-error"
      type="email"
    />
    <p id="email-error">Enter a valid email address.</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. - 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/no-assertive-status: Status live region interrupts assistive technology
react-doctor/no-autofocus: Disallow the autoFocus prop — stolen focus disorients screen-reader and keyboard users.
react-doctor/no-autoplay-without-muted: Autoplaying media without muted
react-doctor/no-blocked-paste: Paste blocked in an authentication field
react-doctor/no-cramped-container-padding: Bounded text container has cramped padding

react-doctor/no-aria-invalid-without-description