How to fix region on Webflow

Steps for Webflow

1. Open your project in the Webflow Designer. In the Navigator panel (left sidebar), locate the outermost structure of your page.
2. Select the site header/navbar element, open its Settings panel (right sidebar), and change its HTML tag from `Div` to `Header` using the Tag dropdown — Webflow will output `<header>` which browsers map to `role="banner"` automatically.
3. Select the main content wrapper `Div`, change its tag to `Main` — this outputs `<main>` with the implicit `role="main"`.
4. Select the footer element and change its tag to `Footer` (outputs `<footer>` with implicit `role="contentinfo"`).
5. For any standalone content sections (e.g. a promo banner `Div` outside the main wrapper), select it, change its tag to `Section`, then open the Element Settings panel and add a custom attribute: Name = `aria-label`, Value = `[Section purpose, e.g. Promotional Banner]`. This gives it an explicit landmark.
6. Publish the site, then run axe DevTools on the live or staging URL to confirm all content is inside landmarks.

<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.