Accessibility fix guide
No ARIA Landmarks Detected
No landmark regions found. Screen reader users rely on landmarks (main, nav, header, footer) to navigate page sections quickly.
Issue ID: A11Y-LANDMARKS-001
Severity: medium
Impact: Med
Effort: S
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
No landmark regions found. Screen reader users rely on landmarks (main, nav, header, footer) to navigate page sections quickly.
Why it matters
No landmark regions found. Screen reader users rely on landmarks (main, nav, header, footer) to navigate page sections quickly. This affects usability, compliance risk, and how many visitors can successfully consume the page.
How we detect it
- FreeSiteAudit flags this issue when the rule for A11Y-LANDMARKS-001 fails and the page evidence points to Dom body.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Use semantic HTML5 elements: <main>, <nav>, <header>, <footer>, <aside>
- 2Or add ARIA role attributes: role="main", role="navigation", role="banner", role="contentinfo"
- 3Ensure the main content is wrapped in <main> or role="main"
How to re-check it
- Use a screen reader or accessibility checker to confirm landmarks are present
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.