# Contentinfo landmark should not be contained in another landmark > Canonical HTML version: https://rocketvalidator.com/accessibility-validation/axe/4.11/landmark-contentinfo-is-top-level > Attribution: Rocket Validator (https://rocketvalidator.com) > License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Landmarks are one of the primary ways screen reader users orient themselves on a page and navigate between major sections. The `contentinfo` landmark is specifically intended to hold site-wide footer information — copyright notices, privacy policies, contact links, and similar content. Screen readers like JAWS, NVDA, and VoiceOver provide shortcut keys that let users jump directly to landmarks by role. When a `contentinfo` landmark is nested inside another landmark (such as `main` or `navigation`), it no longer appears as a top-level landmark in the screen reader's landmark list. This means blind and deafblind users may not be able to find the footer information efficiently, or they may encounter it unexpectedly while navigating a different section of the page. The organizational benefit of landmarks is undermined when they are improperly nested. This rule is a Deque best practice aligned with the broader principles of proper landmark usage recommended by the W3C's ARIA Landmarks specification. While not mapped to a specific WCAG success criterion, correct landmark structure supports WCAG 1.3.1 (Info and Relationships), WCAG 2.4.1 (Bypass Blocks), and the overall goal of providing a clear, navigable document structure. ## How to Fix It 1. **Locate your `contentinfo` landmark.** This is either a `