acc
How to fix: ARIA landmark regions (WCAG 1.3.6 AAA)
Why this matters
Landmarks (<main>, <nav>, <header>, <footer>) let screen-reader users jump between page regions with one keystroke. Without them, the page is one undifferentiated wall of content. WCAG 1.3.6 is Level AAA but the practical impact is on every screen-reader visit.
Background
Landmarks let screen-reader users jump between page regions with one keystroke. HTML5 semantic elements have implicit landmark roles. WCAG 1.3.6 is Level AAA but landmarks are widely used across A and AA conformance.
References
WCAG 2.1 SC 1.3.6 Identify Purpose (AAA) · ARIA Authoring Practices
How to fix
Code snippet for each stack we cover. Pick the one matching your server / framework.
nginx
No server config.
apache
Same.
cloudflare
Same.
wordpress
Wrap your page sections in <header>, <main>, <nav>, <footer>. Modern themes do this; older / page-builder themes wrap everything in <div>s.
flask
Refactor base template to use semantic elements: <header>, <main role="main" id="main">, <nav>, <footer>.
express
Same.
rails
Same.
Verify it's working
Browser devtools: document.querySelector('main') + 'nav' + 'header' + 'footer' should each return an element.
Want to know if your site has this issue?
Run a free 53-check audit — security, GDPR, NIS2, and technical SEO.
Audit my site →