Skip to content
Pandus

Recommended practice Priority: Minor

The page has more than one main footer

The page marks several areas as the site footer, for example the shop footer and a second footer inside a pop-up or widget. This is a recommended practice that goes beyond the WCAG 2.2 AA level the law relies on.

This text was translated automatically and has not been reviewed by a native speaker yet.

Why it matters to your customers

Screen reader users jump between page areas (header, menu, main content, footer) like chapters of a book. With two footers they cannot tell which one holds your contact details, returns policy and legal links, and may give up looking.

Who is affected

  • blind people using screen readers
  • people who navigate by page areas with a keyboard
  • older customers using assistive tools

How to fix it

Keep exactly one site-wide footer: a <footer> that is a direct part of the page body (not inside <article>, <section>, <main> or <aside>) or one element with role="contentinfo". Remove role="contentinfo" from any other block, and turn extra footers placed at page level into plain <div> elements or move them inside the section they belong to.

On Shopify

Usually caused by a footer section added twice or an app that injects its own <footer>. Check the footer group in layout/theme.liquid and the sections it renders; ask the app developer to use a <div> instead.

On Shoptet (CZ)

Usually comes from the template or a custom code snippet added to the footer. Check your own added HTML first; if the duplicate is in the template, report it to Shoptet or a partner.

On PrestaShop

Usually the theme's footer template plus a module that outputs another <footer> at page level. Edit the module's template override in the theme, or the theme's footer .tpl file.

On WooCommerce

Usually a page builder footer template plus the theme's own footer, or a plugin adding role="contentinfo". Disable one of the footers in the builder or theme settings, or fix the markup in the child theme's footer.php.

Standards

Not a WCAG success criterion: a recommended practice that makes the site easier to use.

Automated check: axe-core rule landmark-no-duplicate-contentinfo. dequeuniversity.com, github.com, www.w3.org

All rules we check