Prevent keyboard trap in drilldown subnav #12038
Closed
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.
I have created a new pull request from my personal Github account. It is required that a pull request be opened from a personal account in order to allow edits from maintainers. The original pull request was opened from the utulsa team account.
This replaces #12025
Description
While the tab key moves focus appropriately in the dom order within this component. The focus is not visually discernible when the subnav is opened. Since the method to move back up within the dom tree is present via arrow keys and the link at the top of the subnav, I agree with the solution that was proposed in Drilldown Sub-Menus won't let you Tab/Shift Tab out of Sub-Menu #11641
Broad information about keyboard best practice can be found here: https://www.w3.org/TR/wai-aria-practices/#kbd_generalnav
This will remove it from the dom allowing the user to tab into the next component/area when the subnav is open/visible
Add .visible class for use in drilldown subnav when opened.
These changes are recommented by https://github.com/ntdonley in #11641
...
Types of changes
Checklist
develop
ordevelop-v...
).