You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The reason will be displayed to describe this comment to others. Learn more.
Generally the onKeyPress works well with simple Popover controls. It gets a bit tricky with complex controls like ComboboxInput, LocalizationEditor, SearchInput because they have additional input and button within.
Once the Popover is open - how do I navigate inside of it with keyboard? Or is that out of scope for this pr.
I forgot to turn keycastr on but I tabbed to the button dropdown and then was using the arrow keys - not the mouse like it looks. Bad gif sorry!
@jbadan keyboard navigation for Popover is through tabbing in #793
I would think that a basic Popover should navigate via tabbing since it can contain any content, but it makes sense that certain compositions (Dropdown, ComboboxInput, etc.) would use arrow keys. Probably out of scope for now.
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.
Description
Add accessibility features to the
Popover
control
prop. This way, any element can be passed as a control, but it will still work as a button.tabIndex
: puts normally non-tabbable elements into the normal tab flowaria-haspopup
: indicates the button triggers a popuprole="button"
: screenreader will announce element as buttononKeyPress
handler: if thecontrol
is not a button, addsenter
andspace
as a way to trigger the popover.