How to fix region on Squarespace

Steps for Squarespace

1. Squarespace controls its HTML output through its built-in templates; you cannot change core landmark tags directly. First, verify you are using a modern Squarespace template (Fluid Engine / 7.1) — these output better semantic HTML than legacy 7.0 templates.
2. In the Pages panel, ensure every page has a Header and Footer enabled (Pages → [Page] → Page Settings → check that header/footer are not hidden), as Squarespace maps these to `<header>` and `<footer>` landmark roles.
3. Go to Design → Custom CSS to add CSS only — you cannot inject landmark tags via CSS, so for missing `<main>` or `role` attributes you must use Code Injection: go to Settings → Advanced → Code Injection and add a `<script>` that sets `document.querySelector('#page')?.setAttribute('role', 'main')` as a stopgap until Squarespace fixes its template output.
4. For individual pages, use the Page Header / Page Content blocks and keep all content sections within the page canvas (not injected via footer code injection) so they fall inside Squarespace's main content wrapper.
5. Re-run axe DevTools after each change to verify improvement; note that some landmark issues on Squarespace require a template update from Squarespace itself.

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