How to fix region on Adobe Commerce (Magento)

Steps for Adobe Commerce (Magento)

1. Landmark structure lives in your active theme's layout XML and PHTML templates. Navigate to `app/design/frontend/[Vendor]/[Theme]/Magento_Theme/templates/` (or the equivalent in `vendor/magento/` if you haven't overridden it).
2. Open `html/header.phtml` and ensure the outermost element is `<header role="banner">` (or add the `role` attribute if the tag is a `<div>`).
3. Open `html/footer.phtml` and ensure it uses `<footer role="contentinfo">`.
4. In your theme's `default.xml` layout file (`Magento_Theme/layout/default.xml`), confirm the main content container block renders inside a `<main>` tag. If not, override the `1column.phtml` / `2columns-left.phtml` templates under `Magento_Theme/templates/html/` and wrap the main column in `<main id="maincontent" role="main">`.
5. For CMS blocks or widgets that render outside these landmarks (e.g. a full-width promo strip injected above the header block), edit the CMS block HTML in Content → Blocks → [Block Name] and wrap the content in `<section role="region" aria-label="[Description]">...</section>`.
6. Run `bin/magento cache:clean`, then use axe DevTools on the frontend to verify all violations are resolved.

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