How to fix region on Magento Open Source
Wrap all visible page content inside HTML landmark regions (e.g. `<header>`, `<main>`, `<nav>`, `<footer>`) so screen-reader users can navigate the page by section.
Steps for Magento Open Source
- Follow the same steps as Adobe Commerce (Magento) above — the theme and template architecture is identical.
- If you are on an older Magento 2 version without a heavily customized theme, check that the default Luma or Blank theme's 'root.phtml' already includes landmark tags; if you have overridden it without them, add them as described above.
What is region?
Landmark regions are special HTML tags — like `<header>`, `<main>`, `<nav>`, `<aside>`, and `<footer>` — that divide a page into named zones. Screen readers and assistive technologies use these zones as a navigation menu, letting users jump straight to the area they need (e.g. "skip to main content") instead of listening to every element. The WCAG "region" rule fails when any visible content sits outside of all these landmark zones — meaning a portion of your page is effectively invisible to screen-reader navigation.
Approximately 7 million Americans rely on screen readers, and "landmark navigation" is one of the primary ways they move through a web page. When content sits outside landmarks, those users cannot find or reach it at all — a direct barrier that can expose your store to accessibility lawsuits under the ADA (Title III) and similar laws in Canada, the UK, and the EU. Beyond legal risk, accessible stores convert better: removing navigation barriers keeps more users on the page and completing purchases. Google also uses page structure as a quality signal, so a well-structured landmark layout can reinforce your SEO.
See the complete Region guide for every platform and the full background.
Not sure if your Magento Open Source store has this?
Run a free SEOLZ scan — we’ll find region and every other issue across your whole site.
Scan my site free