| Rule ID |
Landmark 3 |
| Definition |
Each page in a website must have at least one navigation landmark, used to identify website navigation links. |
| Purpose |
- Navigation landmarks provide a way to identify groups (e.g. lists) of links that are intended to be used for website or page content navigation.
|
| Mappings |
-
HTML5 and ARIA Techniques
(Required)
|
| WCAG Success Criteria |
2.4.1 Bypass Blocks (Level A, Primary Success Criterion)
Other Related Success Criterion:
|
| Rule Category |
Landmarks |
| Scope |
Website |
| Target Resources |
[role="navigation"] or top-level nav element
|
| Techniques |
- Reserve the
navigation landmark for website and page navigation links.
- Website and page navigation links should be top-level
navigation landmarks (i.e. not contained in other landmarks).
- The
nav element or an element with role="navigation" attribute defines a navigation landmark and must be on a container element (e.g., div) for ol and ul elements that contain li elements with links. (This may require adding a container element.)
- If there is only one
navigation landmark on the page, do not use a label.
- If there is more than one
navigation landmark, use the aria-labelledby, aria-label oe title attribute to describe the purpose of the links (e.g., Table of Contents, Site Map, etc.) contained in each.
- If the same set of links is used in more than one place on a page, use "Copy 1", "Copy 2" ... "Copy N" as a part of the accessible name to make the navigation labels unique and help orient assistive technology users that the group of links is repeated on the page.
|
| Manual Checks |
- A list of links to other pages in the website, or to content sections of the current page, should use a
navigation landmark.
- Verify the links are used for website or page navigation purposes.
- Verify the labels uniquely identify each set of navigational links.
|
| Informational Links |
|