How to fix landmark complementary is top level 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 the relevant template file where the sidebar appears — typically `sidebar.php`, `page.php`, `single.php`, or `archive.php` in your active (child) theme folder.
3. Locate the `get_sidebar()` call or the `<aside id="secondary"…>` block. If it sits between the opening and closing `<main>` tags, move it outside: place the `get_sidebar()` call after the closing `</main>` tag and before `</div>` of any wrapper.
4. In the corresponding template (e.g., `page.php`), ensure the structure reads: `<div class="content-area"> <main id="main">…</main> <?php get_sidebar(); ?> </div>` — both `<main>` and the sidebar `<aside>` are siblings inside the wrapper.
5. Apply Flexbox or Grid in your child theme's `style.css` to `.content-area` so the columns render correctly without changing the DOM nesting.
6. Add `aria-label="Sidebar"` (or a more specific label) to the `<aside>` in `sidebar.php`, update the files, and run axe DevTools or WAVE to confirm the fix.

What is landmark complementary is top level?

Landmarks are special HTML "signposts" that screen readers use to let users jump directly to major sections of a page — the header, main content, navigation, footer, and sidebars. The "complementary" landmark (created by an `<aside>` tag or `role="complementary"`) is meant to mark supporting content that stands on its own alongside the main content, like a sidebar, related-links panel, or promotional widget. The WCAG rule "landmark-complementary-is-top-level" fires when that `<aside>` is placed inside another landmark (for example, inside a `<main>`, `<header>`, or `<section>` with a role), rather than sitting directly inside the `<body>` at the top level of the page.

Screen reader users — including customers with visual impairments — rely on landmark navigation to quickly skip around a page without listening to everything. When a complementary landmark is buried inside another landmark, screen readers either misreport its purpose or completely hide it from the landmark list, making it impossible for these users to find your sidebar content (promotions, related products, trust badges, support widgets) efficiently. This is a WCAG 2.1 Success Criterion 1.3.6 (Identify Purpose) and best-practice landmark structure issue, and repeated accessibility failures create legal exposure under laws like the ADA (US), EAA (EU), and AODA (Canada). Fixing it improves the experience for the roughly 7 million screen reader users in the US alone, reduces legal risk, and signals to Google that your page is well-structured.

See the complete Landmark complementary is top level guide for every platform and the full background.