# All page content should be contained within landmarks. > Canonical HTML version: https://rocketvalidator.com/accessibility-validation/accesslint/0.16/landmarks/region > Attribution: Rocket Validator (https://rocketvalidator.com) > License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Screen reader users rely on landmarks to navigate through a page. Landmarks act as structural signposts, allowing users to jump directly to sections like the main content, navigation, or footer without reading through every element in sequence. When content sits outside any landmark region, screen readers may skip it entirely or present it as orphaned content with no structural context, making it harder to find and understand. This rule checks that all visible page content is contained within an appropriate landmark element. Content that falls outside landmarks is effectively invisible to landmark-based navigation, which is one of the primary ways assistive technology users move through a page. This issue relates to WCAG Success Criterion 1.3.1 Info and Relationships (Level A), which requires that the structure and relationships conveyed visually are also available programmatically. When content lacks a landmark container, the structural relationship between that content and the rest of the page is lost for assistive technology users. ## Which landmarks to use HTML5 introduced semantic elements that automatically map to ARIA landmark roles: - `
` (when not nested inside `
` or `
`) maps to `banner` - `