Skip to content
New issue

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

Add note on use of ARIA to uniquely identify nav elements #5646

Open
schalkneethling opened this issue Jun 15, 2020 · 0 comments
Open

Add note on use of ARIA to uniquely identify nav elements #5646

schalkneethling opened this issue Jun 15, 2020 · 0 comments
Labels
accessibility Affects accessibility clarification Standard could be clearer

Comments

@schalkneethling
Copy link
Contributor

schalkneethling commented Jun 15, 2020

In the documentation linked to below, a common usage pattern of the nav element is discussed. There is however no mention of using either aria-label or aria-labelledby to convey the purpose of each navigational aid and also distinguish them from each other.

While there is a link provided to ARIA in HTML for authors[1] this also does not mention this pattern. Adding an entire section to the HTML docs around this might not be appropriate but, perhaps a short mention and a link to the ARIA landmark docs[2] is possible?

Something like:

Accessibility note: It is a common design pattern to uniquely label each nav element when there is more than one on a page. Read more

1 - nav element ARIA in HTML entry
2 - Navigation landmark docs

Linked Docs Section

https://html.spec.whatwg.org/commit-snapshots/31b264a56253e7b047d1cc6a02a4c6337dd6cff5/#the-nav-element

In the following example, there are two nav elements, one for primary navigation around the site, and one for secondary navigation around the page itself.

@annevk annevk added accessibility Affects accessibility clarification Standard could be clearer labels Jun 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Affects accessibility clarification Standard could be clearer
Development

No branches or pull requests

2 participants