Skip to content

Accessibility

Why a page needs a main landmark

A main landmark is what lets someone jump straight to the content instead of walking through the header on every page. Without one, assistive technology has no reliable way to identify where the page's own content begins.

What 13x checks

This is rule accessibility.landmarks in the public registry: Page has a main landmark. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.

Surface
Accessibility
Score weight
4 of the readiness score
Scope
Reported as skipped when the page renders only with JavaScript
Applies
To every site

Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.

The fix

The same text the audit hands you when this check fails on your own site.

Wrap the content in landmarks so a screen reader user can skip past your navigation:

html code
<body>
  <header>…</header>
  <nav aria-label="Main">…</nav>

  <main id="main">
    <!-- page content -->
  </main>

  <footer>…</footer>
</body>

Pair it with a skip link as the first focusable element:

html code
<a href="#main" class="sr-only focus:not-sr-only">Skip to content</a>

One <main> per page. Without it, someone using a screen reader hears your entire menu read out on every page before reaching the content.

Does your site have this problem?

13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.

No signup. Results in 30 seconds.

More accessibility checks