How to fix landmark no duplicate contentinfo on Webflow

Steps for Webflow

1. Open your project in the Webflow Designer. In the Navigator panel (left sidebar), locate the Footer component — it is typically a Section or Div Block with a Tag set to <footer>.
2. Click the Footer element, then in the Element Settings panel (right sidebar, gear icon), confirm the HTML Tag is set to 'footer'. There should be exactly one such element per page.
3. Search the Navigator for any other elements whose tag is set to 'footer' or that have a custom attribute role="contentinfo". Select each duplicate, change its HTML Tag to 'div', and add an aria-label attribute if it needs a descriptive name.
4. If a third-party embed (Embed widget) injects a <footer> or role="contentinfo", click the Embed element, edit the HTML code, and replace <footer> with <div>.
5. Publish the site and test with axe DevTools on the published URL.

What is landmark no duplicate contentinfo?

Every webpage has structural "landmarks" — invisible signposts that screen readers and assistive technology use to navigate the page. The `contentinfo` landmark marks the site-wide footer: the area containing copyright notices, legal links, contact details, and similar site-level information. This landmark is created automatically by an HTML `<footer>` element that is a direct child of `<body>`, or explicitly by adding `role="contentinfo"` to any element. The rule is simple: a page should have exactly one `contentinfo` landmark. If your page contains two or more (for example, a sticky footer widget in addition to your main footer, or a chat widget that injects its own `<footer>`), assistive technology gets confused about which one is the "real" site footer.

Screen reader users — an estimated 7–8 million people in the US alone — rely on landmark navigation to jump directly to page sections without listening to every word. When two `contentinfo` landmarks exist, screen readers either announce both confusingly or skip one entirely, making it harder for visually impaired shoppers to find your return policy, contact information, or legal pages. Beyond accessibility and the real legal risk of ADA/WCAG non-compliance lawsuits (which have steadily increased year-over-year for ecommerce sites), Google's crawler also uses semantic page structure as a quality signal — clean, well-structured HTML is associated with better crawling and indexing. Fixing this issue is also a prerequisite for passing WCAG 2.1 Success Criterion 1.3.6 (Identify Purpose), which is increasingly required by law in the EU, UK, and US.

See the complete Landmark no duplicate contentinfo guide for every platform and the full background.