landmark-unique
Web validation
Landmark regions let assistive technology users jump straight to areas like navigation, form, or search. When more than one region of the same type exists, each must be uniquely identified so users can tell them apart. Using the same role-name pair twice confuses screen reader lists and slows down orientation. Giving every landmark a distinct accessible name also helps people with cognitive or memory-related disabilities keep track of where they are and what each region does. Unique identification therefore supports faster navigation, clearer page structure, and a smoother experience for everyone relying on landmarks.
Pass Patterns
A single instance of a landmark role
Only one <header> region appears on the page, so no additional name is needed.
<header>
<!-- page header -->
</header>Multiple landmarks of the same role with unique names
Each <nav> landmark shares the role navigation but has a unique aria-label, allowing assistive technologies to list them separately.
<nav aria-label="Primary">
<!-- main site links -->
</nav>
<nav aria-label="Secondary">
<!-- secondary links -->
</nav>Fail Patterns
Duplicate landmark roles without names
Screen readers will announce two indistinguishable navigation landmarks, forcing users to explore both to learn their purpose.
<nav>
<!-- links group one -->
</nav>
<nav>
<!-- links group two -->
</nav>Repeated names on identical roles
The duplicate aria-label “Subscribe” prevents users from knowing which form is which.
<form aria-label="Subscribe">
<!-- email signup -->
</form>
<form aria-label="Subscribe">
<!-- feedback form -->
</form>Try It Yourself
Using a screen reader
New to screen reader testing, or need a refresher?
Review this article first: Practical guides for using screen readers
- Open the page in a desktop screen reader.
- Open the screen reader’s elements list (NVDA
Insert+F7, VoiceOverControl+Option+U), and go to the “Landmarks” section.
Expected results: Landmark elements of the same type have unique names.
Actual results: Multiple landmark elements of the same type have no name or have the same name.
FAQ
Why is this rule considered a best practice?
WCAG does not directly require unique landmark names, yet distinct identification greatly improves landmark navigation and orientation in assistive technology lists. Adopting this pattern aligns with the WCAG principle of perceivable content and supports smoother user journeys.
Why is this issue marked as Moderate?
While the page remains operable, duplicated landmark names slow down orientation, especially for screen reader and keyboard users. The accessibility barrier can cause frustration and navigation errors but does not fully block access, so the impact is moderate.