Support Article
Accessibility testing - Ensures landmarks are unique
SA-97120
Summary
During Accessibility testing with the Axe tool, the 'Landmarks should be unique' error message displays in the Axe console.
Error Messages
From the Axe console:
|
Impact |
Landmark-unique is a new best practice rule ensures that landmarks have a unique role or accessible name (i.e. role, label, title) combination. |
| Severity | Medium |
| Required Correction |
Landmarks must have a unique role or role/label/title (i.e. accessible name) combination Element location #l1 Element source <header id="l1" class="screen-layout-region screen-layout-region-header not-nav" aria-label="Top Panel" role="banner"> To solve this violation, you need to: Fix the following: The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable Related node: #PegaGadget1Ifr header |
Steps to Reproduce
- Log in as a user.
- Create any case.
- Run the Accessibility test on the screen (use any tool or Chrome extension such as 'Axe'). Error displays.
Root Cause
The field value was the same for both the portal and the work area harness. Hence the same label was set for all aria-labels.
Resolution
Perform the following local-change:
The aria-label used for screen layout various regions relies on their respective field values.
For example, to set the aria-label in the top panel, refer to the 'Top Panel' field value. Refer to the 'Left Panel' to set the aria label of the left panel and so on.
To set a unique value for aria-labels perform the following steps,
- Save As the field values.
- Add property references (for example, Top Panel for {.pyLabel}).
- Set the pyLabel accordingly on the primary page.
Published February 12, 2020 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.