Rule

Regions with a purpose

The purpose of page regions should be programmatically determinable (AAA)

Rule
region-purpose
WCAG 2.2
1.3.6 Identify Purpose (opens in a new tab) (Level AAA)
Severity
Moderate

What it checks

At Level AAA, the purpose of page regions should be available to software. Landmarks are how a page does that: <main>, <nav>, <header>, <footer>, <aside>, <search>, a labelled <section> or form, and the matching ARIA roles. The rule asks once per page, and a page with at least one landmark passes.

When a person decides

A page with no landmark at all is sent for review rather than failed, because the criterion allows other ways to expose purpose that the markup does not show. The purpose of components and icons is part of the same criterion, and a person needs to check it on every page.

Example

Sent to review

<div class="top">
  <a href="/">Home</a> <a href="/about">About</a>
</div>
<div class="content">
  <h1>Opening times</h1>
  <p>Open daily from nine.</p>
</div>

Passes

<nav aria-label="Main">
  <a href="/">Home</a> <a href="/about">About</a>
</nav>
<main>
  <h1>Opening times</h1>
  <p>Open daily from nine.</p>
</main>

The engine is tested against both examples.

How to fix it

Wrap the page's regions in <header>, <nav>, <main>, <aside> and <footer>, or the matching ARIA roles.

Check your own pages

This rule runs in every pour audit: the browser extension, the bookmarklet, the command line and the editor. Get pour, free.