How to fix region on Wix

Steps for Wix

1. Wix generates HTML automatically and does not let you edit raw HTML directly in standard Wix Editor. Your best path is: in the Wix Editor, ensure every page has a recognizable Header section (the built-in Wix Header component) and Footer section — Wix maps these to `<header>` and `<footer>` landmarks automatically.
2. Make sure all body content is placed inside Wix 'Section' containers on the page canvas, not floating above the header or below the footer — Wix sections render inside the main content area.
3. For any 'Strip' or 'Box' elements outside the main body area, move them onto the canvas between header and footer using the Editor's drag-and-drop.
4. If you use Wix Studio (the developer-facing editor), open the page's Velo code panel and use `$w.onReady()` to verify the DOM structure, or add custom HTML components with `<section role="region" aria-label="...">` via the HTML iframe embed widget for content that needs explicit landmark roles.
5. Install the 'Accessibility Wizard' from the Wix App Market (free) to surface remaining landmark issues, then re-test with axe DevTools.

<header role="banner">
  <nav aria-label="Main menu"><!-- navigation links --></nav>
</header>

<main id="main-content" role="main">
  <!-- all primary page content goes here -->
</main>

<aside role="complementary" aria-label="Promotions">
  <!-- sidebar or supplementary content -->
</aside>

<footer role="contentinfo">
  <!-- footer links and legal text -->
</footer>

<!-- If a div cannot become a semantic element: -->
<div role="region" aria-label="Customer Reviews">
  <!-- review content -->
</div>

What is region?

Landmarks are special HTML tags or ARIA attributes that divide a web page into named regions — like the main content area, navigation menu, page header, and footer. Screen readers and other assistive technologies use these regions as a table of contents, letting users jump directly to the part of the page they need. When content sits outside any landmark, assistive technology users cannot locate or skip to it. This is what the "region" accessibility rule checks: it flags any significant block of content that is not wrapped in one of these landmark containers.

Approximately 7 million Americans use screen readers, and landmarks are one of the most fundamental navigation tools they rely on. Without them, a screen-reader user must listen to your entire page linearly just to find the product listing or checkout button — a frustrating experience that causes them to leave. Beyond lost sales, WCAG 2.1 Success Criterion 1.3.6 (and the broader WCAG framework) requires content to be programmatically determinable; failure exposes your store to ADA/Section 508 accessibility complaints and litigation, which are rising year-on-year in the US and EU (EAA 2025). Search engines also use landmark structure to understand page hierarchy, so fixing this can modestly reinforce your on-page SEO signals as well.

See the complete Region guide for every platform and the full background.