We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<nav>
The following <nav> elements need accessible names (i.e. can be set with aria-label or aria-labelledby).
aria-label
aria-labelledby
Use aria-label to set accessible names for these regions. Do not use the word “navigation” in the name (it’s redundant).
When there’s more than one navigation region on a page, they should have accessible names to distinguish them from each other.
These unnamed navigation regions might appear more prominent than they should be.
No response
HEAD
The text was updated successfully, but these errors were encountered:
knowler
Successfully merging a pull request may close this issue.
Terms
Description
What's wrong?
The following
<nav>
elements need accessible names (i.e. can be set witharia-label
oraria-labelledby
).Possible solutions
Use
aria-label
to set accessible names for these regions. Do not use the word “navigation” in the name (it’s redundant).References
Steps To Reproduce
Expected Behavior
When there’s more than one navigation region on a page, they should have accessible names to distinguish them from each other.
Actual Behavior
These unnamed navigation regions might appear more prominent than they should be.
Relevant Log Output
No response
Versions
HEAD
The text was updated successfully, but these errors were encountered: