Writing Accessible Landmark Labels
Writing Accessible Landmark Labels replaces an already-owned input-format topic with a distinct APG-supported wording task for naming repeated page regions.
When the same landmark role appears more than once, give instances concise distinguishing labels and avoid redundantly including the role name in the label.
Key details
Important caveats
Scope Boundary
This page covers label wording for landmarks; choosing roles and applying aria-label or aria-labelledby are implementation concerns.
Further guidance
Content
Give repeated landmarks concise labels that distinguish their purpose, and avoid repeating role words such as “navigation” when the role will already be announced.
Practical Application
When the same landmark role appears more than once, give each instance a short label that distinguishes its purpose, and omit the role word itself when assistive technology will announce that role.
Purpose
Distinct labels help users tell multiple landmarks of the same role apart during page navigation.
Reader Check
Would the labels still distinguish the repeated regions when read as “navigation, [label]” or “region, [label]”?
Worked Example
Example: For two navigation landmarks, use labels such as “Primary” and “Account” rather than “Primary navigation” and “Account navigation.”
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Landmark Regions — WAI-ARIA Authoring Practices Guide (opens in a new tab)World Wide Web Consortium (W3C) · W3C APG guidance for unique, non-redundant landmark labels.