How to fix landmark unique on Wix

Steps for Wix

1. Wix does not expose direct HTML editing for structural landmark elements like <nav> through the standard editor.
2. Open the Wix Editor and select your navigation menu widget; in the Settings or Accessibility panel (the person icon), look for an 'ARIA label' or 'Accessible name' field and enter a unique label.
3. For Wix Studio, select the component, open the Properties panel, and use the Accessibility section to add a custom aria-label.
4. For elements where no built-in ARIA field exists, add a Wix Velo (code) solution: in the Page Code panel, use $w('#menuId').setAttribute('aria-label', 'Primary navigation'); for each navigation component.
5. Contact Wix Support if landmarks are generated by Wix's own theme infrastructure and cannot be labelled through any of the above routes — this may require a platform-level fix.

<nav aria-label="Primary navigation">
  <!-- main site menu links -->
</nav>

<nav aria-label="Breadcrumbs">
  <!-- breadcrumb trail -->
</nav>

<!-- OR, using a visible heading already inside the landmark -->
<aside aria-labelledby="related-products-heading">
  <h2 id="related-products-heading">Related Products</h2>
  <!-- product cards -->
</aside>

What is landmark unique?

Landmarks are special HTML elements — like `<nav>`, `<header>`, `<footer>`, `<main>`, `<aside>`, and `<section>` — that act as signposts letting screen-reader users jump quickly around a page. When the same type of landmark appears more than once on a page (for example, two `<nav>` elements: one for the main menu and one for breadcrumbs), each one must have a distinct label so users know which is which. Without that label, a screen reader just announces "navigation" twice, leaving users unable to tell them apart. The fix is to add an `aria-label` attribute (e.g. `aria-label="Main menu"` and `aria-label="Breadcrumbs"`) or an `aria-labelledby` pointing to a visible heading inside the landmark.

For the roughly 7.5 million Americans who use screen readers, duplicate unlabelled landmarks make navigation genuinely confusing or impossible — they cannot tell which "navigation" or "complementary" region is which. This is a WCAG 2.1 failure (Success Criterion 1.3.6 / best practice under 2.4.1), which creates legal accessibility risk under the ADA, the UK Equality Act, and equivalent laws worldwide. Beyond legal exposure, an inaccessible store loses sales from disabled shoppers — an estimated $490 billion in disposable income in the US alone. Google also uses landmark structure as a crawl signal for understanding page architecture, so clean, labelled landmarks can marginally improve how Googlebot interprets your content hierarchy.

See the complete Landmark unique guide for every platform and the full background.