Content sits outside any landmark region
Automated check region, run with axe-core
- WCAG
- Best practice: a recommendation, not a WCAG success criterion
- Severity
- Moderate: a degraded experience
- Typical effort
- Moderate, 1 to 4 hours
- Category
- Page structure
Who this affects
Screen reader users navigating by region.
Why it matters
Orphaned content is hard to find when navigating structurally, and suggests the page is built from generic divs rather than semantic HTML.
How to fix it
Use <header>, <nav>, <main>, <footer> and <aside> so all content falls inside a landmark.
Check your own website
The free scan tests 3 pages against WCAG 2.2 A and AA in about 30 seconds. No sign-up.