Remove ARIA labels from containers #405
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What’s changed
This PR removes unnecessary ARIA labels from the menu container and the main content window.
These aria-labels are used incorrectly as they are applied to
<div>elements with no role. This is not permitted under the ARIA specification as a<div>has a role ofgeneric. They are also unnecessary as:<nav>element already has an appropriate labelmainlandmark and so an aria-label is unnecessary for its container. We could move the aria-label to<main>instead but while permitted, my understanding is that it would be unnecessary.I've tested it locally using VoiceOver and:
mainlandmark is correctly identified asmainI believe this fixes #404 .
Identifying a user need
This came out of testing by Shabana Ali in the WCAG Primer working group, who identified the incorrect ARIA usage. We believe fails Web Content Accessibility Guidelines (4.1.2 Name, Role, Value - level A)