Skip to content

Commit 4c4ead3

Browse files
authored
Update navigation-has-label.md
1 parent c7ae8c7 commit 4c4ead3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/rules/accessibility/navigation-has-label.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,11 @@ An accessible name ensures that one can distinguish between multiple navigation
88

99
If the navigation area begins with a heading, use the heading to label the navigation element using the `aria-labelledby` attribute. If there is no heading, then you may set `aria-label`. Make sure to format the text the same way you would visual text (Related: [aria-label is well formatted](./aria-label-is-well-formatted.md)).
1010

11-
### Assess whether a navigation landmark should be used at all
11+
### Be wary of inappropriate navigation landmarks ⚠️
1212

1313
This rule will flag all navigation landmarks that don't have an accessible name. However, in some instances, a navigation landmark may be inappropriately used. While addressing this rule, please assess whether or not the instance you're looking at _should_ be a navigation landmark, and follow-up accordingly.
1414

15-
### Don't include "navigation" in the name
15+
### Don't include "navigation" in the name ⚠️
1616

1717
The accessible name for a navigation landmark should NOT include "navigation" because that would add redundancy and verbosity, since screen readers will already announce the navigation landmark.
1818

0 commit comments

Comments
 (0)