ARIA Landmarks
ARIA landmarks allow screen reader users to navigate directly to major page sections — header, navigation, main content, and footer — without reading through every element. SaaSalyst checks your homepage for landmark roles and semantic HTML elements that provide this navigational structure.
What SaaSalyst Checks
SaaSalyst counts elements with ARIA landmark roles (role='main', role='navigation', role='banner', role='contentinfo') and their HTML5 semantic equivalents (<main>, <nav>, <header>, <footer>). Two or more landmarks earn a pass, one triggers a warning, and zero triggers a failure.
Why This Matters
Screen reader users navigate pages by landmarks the way sighted users scan a page visually. Without landmarks, screen reader users must read through every element sequentially to find the content they want.
Proper landmark usage is a WCAG 2.1 Level A best practice. Using semantic HTML5 elements (<main>, <nav>, <header>, <footer>) provides landmarks automatically — it's primarily a matter of using the right HTML elements rather than adding extra attributes.
Enterprise accessibility audits specifically check for proper landmark structure. Products with clear landmark navigation score higher in accessibility evaluations.
5,114
ADA digital accessibility lawsuits filed in the US in 2025
UsableNet
94.8%
Of websites fail basic WCAG checks
WebAIM Million 2025
77%
Of ADA lawsuits target companies under $25M revenue
AudioEye
How to Fix It
- Wrap your page content in semantic HTML5 elements: <header> for the site header, <nav> for navigation, <main> for primary content, and <footer> for the footer.
- Ensure your <main> element wraps the primary content area. There should be exactly one <main> per page.
- For multiple <nav> elements, add aria-label attributes to distinguish them: <nav aria-label="Main navigation"> and <nav aria-label="Footer navigation">.
- Test landmark structure using browser accessibility tools or screen reader software.
Frequently Asked Questions
How does SaaSalyst check for ARIA landmarks?
SaaSalyst counts elements with ARIA roles (main, navigation, banner, contentinfo) and semantic HTML equivalents (main, nav, header, footer). Two or more landmarks earn a pass.
Do I need ARIA roles if I use semantic HTML?
Semantic HTML5 elements (<main>, <nav>, <header>, <footer>) automatically create landmarks. SaaSalyst detects both approaches, so using proper semantic HTML is sufficient.
How do ARIA landmarks affect my Business Readiness Score?
SaaSalyst rates ARIA landmarks as medium severity in Accessibility. Proper landmark structure improves screen reader navigation and is checked during enterprise accessibility audits.
References & Official Sources
Official regulatory and standards sources relevant to the checks SaaSalyst runs on your site.
- WCAG Overview— W3C
- European Accessibility Act Directive— European Union
- WebAIM Million Annual Report— WebAIM
Check Your SaaS Now — Free
SaaSalyst scans your website in 30 seconds and checks for ARIA Landmarks along with 40+ other business readiness signals.
Scan Your App