`react-doctor/no-skipped-heading-level`

Heading hierarchy skips a level

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-skipped-heading-level. 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 Page = () => (
  <main>
    <h1>Account</h1>
    <section>
      <h3>Billing details</h3>
    </section>
  </main>
);

Corrected pattern

const Page = () => (
  <main>
    <h1>Account</h1>
    <section>
      <h2>Billing details</h2>
    </section>
  </main>
);

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-skipped-heading-level diagnostic in the current repository. Required change: - Keep headings in a continuous hierarchy inside a page or article so assistive navigation reflects the visual structure.

Reference transformation:Before:

const Page = () => (
  <main>
    <h1>Account</h1>
    <section>
      <h3>Billing details</h3>
    </section>
  </main>
);

After:

const Page = () => (
  <main>
    <h1>Account</h1>
    <section>
      <h2>Billing details</h2>
    </section>
  </main>
);

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-small-form-control-text: Form control text is smaller than 16px
react-doctor/no-smooth-scroll-without-reduced-motion: Smooth scrolling ignores reduced motion
react-doctor/no-static-element-interactions: Require static elements with click or key handlers to declare an interactive role, or be replaced with a semantic element.
react-doctor/no-tight-body-leading: Body copy has cramped line spacing
react-doctor/no-tiny-text: Use at least 12px for body content, 16px is ideal. Small text is hard to read, especially on high-DPI mobile screens

react-doctor/no-skipped-heading-level