How to fix landmark no duplicate contentinfo on WooCommerce

Steps for WooCommerce

1. In your WordPress admin, go to Appearance → Theme File Editor (or use a child theme via FTP/SFTP).
2. Open footer.php in your active (child) theme. This file typically contains the single <footer> landmark — confirm it is wrapped in one <footer id="colophon"> or similar element.
3. Search all theme PHP files for additional occurrences of <footer or role="contentinfo" using a code editor search across the theme directory.
4. If a page builder (Elementor, Divi, Beaver Builder) is in use, open the page in the builder, select any footer widget/section, switch to its Advanced tab, find the HTML Tag setting, and change it from 'footer' to 'div'.
5. If a plugin (e.g. a sticky footer bar or chat widget) is injecting a duplicate, check the plugin settings for HTML/accessibility options, or add a small JavaScript snippet in Appearance → Customize → Additional CSS/JS to change its element role: document.querySelector('.plugin-footer-class').removeAttribute('role').
6. Update/save and verify with axe DevTools or WAVE browser extension.

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.