Recommended practice Priority: Minor
The site footer sits inside another page area
The footer region (the "contentinfo" landmark with contacts, legal links and payment information) is nested inside another landmark, such as the main content, instead of standing on its own at the bottom of the page. This is a recommended practice that goes beyond the WCAG 2.2 AA level the accessibility laws rely 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, and often go straight to the footer to find contacts, delivery and returns information or the terms. When the footer is nested inside the main content or another area, it does not show up as a separate chapter, so these shoppers must hunt for information that others find at a glance.
Who is affected
- screen reader users
- shoppers looking for contacts, returns or terms with a screen reader
How to fix it
Place the site's <footer> (or the element with role="contentinfo") directly in the page structure, after <main> and outside any other landmark. A common cause is a page wrapper with role="main" that closes only after the footer, or role="contentinfo" added to a footer inside another landmark. A <footer> inside an <article> or <section> is fine, because it is not treated as the site footer.
On Shopify
The footer section group is usually placed after <main> in layout/theme.liquid. Check that <main> or a custom wrapper with a landmark role is closed before the footer, and that no section adds role="contentinfo" inside the content.
On Shoptet (CZ)
Decided by the template's HTML structure. Check whether a newer template version fixes it; otherwise report it to Shoptet or a partner.
On PrestaShop
Usually in the theme's layout .tpl files that include the footer. Make sure the footer block comes after the main content wrapper is closed and is not inside an element with a landmark role.
On WooCommerce
Usually the theme's footer.php closes the content wrapper too late, or a page-builder footer template sits inside an element with a landmark role. Fix it in the child theme's footer.php or in the builder's footer template.
Standards
Not a WCAG success criterion: a recommended practice that makes the site easier to use.
Automated check: axe-core rule landmark-contentinfo-is-top-level.
dequeuniversity.com, github.com, www.w3.org