How to fix landmark contentinfo is top level on Webflow

Steps for Webflow

1. Open your project in the Webflow Designer.
2. In the Navigator panel (left side), find your Footer section/element. Confirm it sits at the root level of the page structure — a direct child of the Body element, not nested inside a Main Wrapper, Section, or any element that has a landmark role.
3. If the Footer is nested inside a Main Wrapper or other landmark container: click the Footer element in the Navigator, then drag it out to be a direct child of Body (below the Main Wrapper).
4. In Webflow, the built-in 'Footer' element automatically receives the correct semantic role. Ensure you are using the native Footer element type (not a plain Div inside another landmark).
5. Publish the site and verify with the axe DevTools browser extension.

What is landmark contentinfo is top level?

Every webpage typically has a footer that contains things like copyright notices, contact links, and legal disclaimers. In HTML, the `<footer>` tag (or any element with `role="contentinfo"`) is a special navigation landmark that screen readers use to help users jump directly to site-wide footer content. The WCAG rule `landmark-contentinfo-is-top-level` means that this footer landmark must sit at the top level of the page — a direct child of `<body>` — rather than being wrapped inside another landmark element like `<main>`, `<header>`, `<section>`, or `<article>`. When your footer is nested inside another landmark, screen readers get confused about the page's structure and may not correctly announce or navigate to the footer.

Screen reader users — including many people with visual impairments or motor disabilities — rely on landmark regions to skip around a page efficiently, much like sighted users scan headings visually. When your `contentinfo` (footer) landmark is buried inside another landmark, assistive technologies either skip it or mis-announce it, making your site harder or impossible to navigate for these users. This is a WCAG 2.1 failure (Success Criterion 1.3.6 / best practice under 4.1.2), meaning your store may face legal accessibility risk under laws like the ADA (USA), EAA (EU), or AODA (Canada). Fixing it also signals high HTML quality to search engines, which increasingly factor accessibility into crawl quality, and avoids potential legal complaints or demand letters that are increasingly common against ecommerce stores.

See the complete Landmark contentinfo is top level guide for every platform and the full background.