`react-doctor/no-multiple-unlabeled-navigation-landmarks`

Repeated navigation landmarks need unique names

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

Validate the diagnostic

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

Confirm the reported code matches react-doctor/no-multiple-unlabeled-navigation-landmarks. 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

<><nav>Primary links</nav><nav>Account links</nav></>

Corrected pattern

const Page = () => (
  <div>
    <nav aria-label="Sections" />
    <nav aria-label="Account sections" />
  </div>
);

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-multiple-unlabeled-navigation-landmarks diagnostic in the current repository. Required change: - Give each coexisting navigation landmark a concise, unique aria-label or aria-labelledby value.

Reference transformation:Before:

<><nav>Primary links</nav><nav>Account links</nav></>

After:

const Page = () => (
  <div>
    <nav aria-label="Sections" />
    <nav aria-label="Account sections" />
  </div>
);

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-noninteractive-element-interactions: Move the interaction to a semantic interactive element, or add an interactive role plus keyboard support.
react-doctor/no-noninteractive-element-to-interactive-role: Use a semantic interactive element instead of role-promoting a non-interactive one.
react-doctor/no-noninteractive-tabindex: Reserve tabIndex for interactive elements or interactive roles; remove it from non-interactive ones.
react-doctor/no-nonresizable-textarea: Textarea resizing is disabled
react-doctor/no-outline-none: Use `:focus-visible { outline: 2px solid var(--color-muted); outline-offset: 2px }` to show focus only for keyboard users while hiding it for mouse clicks

react-doctor/no-multiple-unlabeled-navigation-landmarks