How to fix landmark contentinfo is top level on Adobe Commerce (Magento)
Move your footer element (or any element with role="contentinfo") to the top level of the page so it is not nested inside another landmark region.
Steps for Adobe Commerce (Magento)
- In your Magento admin, go to Content → Design → Configuration → edit your active theme → HTML Head / Footer settings to inspect global footer markup.
- For theme-level fixes, locate your theme's `Magento_Theme/templates/html/footer.phtml` (or the equivalent file in your custom theme directory under `app/design/frontend/<Vendor>/<Theme>/`).
- Open your layout XML file — typically `Magento_Theme/layout/default.xml` — and confirm the `<footer>` block is declared as a direct child of `<body>`, not inside the `<main>` block.
- If the footer block is assigned as a child of `main` in the layout XML, move its `<referenceBlock>` declaration so it references `root` or the body-level container instead.
- Clear the Magento cache (System → Cache Management → Flush Cache Storage) and validate with axe DevTools.
- If using Page Builder, inspect the generated HTML in the browser and adjust the Page Builder layout to ensure the Footer row/section is outside the Main Content container.
<footer>
<!-- ✅ CORRECT: <footer> is a direct child of <body>,
at the same level as <header> and <main> -->
<p>© 2024 My Store. All rights reserved.</p>
</footer>
<!-- ❌ INCORRECT: <footer> nested inside <main> -->
<main>
<p>Page content here...</p>
<footer> <!-- This fails landmark-contentinfo-is-top-level -->
<p>© 2024 My Store.</p>
</footer>
</main>What is landmark contentinfo is top level?
Every webpage has structural "landmarks" — special regions like the header, main content area, navigation, and footer — that act like a table of contents for assistive technologies. The `contentinfo` landmark is the technical name for a page's footer: the region that typically contains copyright notices, legal links, and contact info. The WCAG rule `landmark-contentinfo-is-top-level` requires that this footer landmark sits at the outermost level of the page's structure (a direct child of `<body>`), rather than being accidentally wrapped inside another landmark like `<main>`, `<article>`, or `<section>`. When it is nested inside another landmark, screen reader users get a confusing, incorrect picture of your page's structure.
Screen reader users — including people with visual impairments — rely on landmarks to jump directly to key page sections without reading every word. When your footer is buried inside another landmark, screen readers may announce it incorrectly (e.g., "footer inside main"), causing real confusion and navigation errors for blind shoppers. This is a WCAG 2.1 failure (specifically related to Success Criterion 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value), which exposes your store to accessibility legal risk — including ADA and EAA complaints — and can harm your brand reputation. Fixing it is a quick code change that immediately improves the experience for assistive technology users and demonstrates good-faith accessibility compliance.
See the complete Landmark contentinfo is top level guide for every platform and the full background.
Not sure if your Adobe Commerce (Magento) store has this?
Run a free SEOLZ audit — we’ll find landmark contentinfo is top level and every other issue across your whole site.
Scan my site free