How to fix landmark no duplicate contentinfo on Shopify

Steps for Shopify

1. Go to Online Store → Themes → click 'Edit code' on your active theme.
2. Open the layout file: Layout/theme.liquid. Look for any <footer> tag near the bottom of the file — this is your main footer landmark.
3. Open Sections/footer-group.liquid or Sections/footer.liquid (name varies by theme) and confirm it contains exactly one top-level <footer> element.
4. Search all section and snippet files (Snippets/) for additional <footer> tags or role="contentinfo" by using the theme editor's search (magnifying glass icon). Change any secondary ones to <div> with an appropriate aria-label.
5. If a third-party app (e.g. a chat widget installed via the App Embed block) is causing the duplicate, go to Online Store → Themes → Customize → App Embeds, open the app's settings, and look for an HTML/accessibility option to disable its own footer wrapper.
6. Save all files and re-test with the axe DevTools 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.