Update tabbing behaviour for Popover component#2418
Draft
cemms1 wants to merge 1 commit into
Draft
Conversation
|
Contributor
|
Tip Once this PR is ready to go, add the This saves us a lot of money by not running the tests before we need them. |
2dacec0 to
15a2448
Compare
Popover component
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 are you changing?
Updates the tab behaviour for the Popover component in
source-development-kitchenso that when the popover is opened, the keyboard focus is trapped within the popover until the user takes an action to dismiss itThe popover can still be dismissed by using the escape key or by clicking the dismiss/close button
Why?
After discussing as a team, it felt more intuitive for keyboard users and those using screen readers for the focus to be trapped when opening the Popover since otherwise the focus moves to the next tabbable component on the page, which can be behind the popover in terms of z-index value. Being able to focus on elements which are not entirely visible on the screen feels like poor UX.
The guidance for this online is mixed and in general suggests that you should only trap focus for "modal" popover content and not for non-modal popovers. This is not technically a modal popover