Elgarde
Violations

Content not within a landmark region

moderate Accessibility WCAG 1.3.1

How common

Common. Many websites lack proper landmark regions, forcing screen reader users to navigate linearly through all content.

What this means

Page content exists outside of any landmark region (<header>, <nav>, <main>, <footer>, etc.). Screen reader users rely on landmarks to jump between sections of a page — content outside landmarks is effectively invisible to this navigation method.

WCAG requirement

Success Criterion 1.3.1 — Info and Relationships: page structure must be programmatically determinable. Landmark regions provide this structure for assistive technologies.

How to fix

Wrap all page content in appropriate landmark elements:

<header><!-- site header, logo, nav --></header>
<nav><!-- main navigation --></nav>
<main><!-- primary page content --></main>
<footer><!-- site footer --></footer>
  • Every page should have exactly one <main>
  • Use <nav> for navigation menus
  • Use <aside> for sidebar content
  • Use <section> with an aria-label for named regions within <main>

Check your website for this violation

Free scan — no registration required. Results in 30 seconds.

Scan now