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
Load the home page and start tabbing through the items until you reach the Swag link
Hit tab one more time, which will take you to #select2-wp20-locale-switcher-container
Hit enter to open the menu
The focus is on the currently selected locale, and you can arrowup / arrowdown to move between them
Hit shift-tab to go to the search field, and it will close the list and take you back to #select2-wp20-locale-switcher-container instead of moving the focus to the search input.
The text was updated successfully, but these errors were encountered:
Oh, huh, the selectWoo demo behaves the same way. The select2 demo focuses the caret in the search field like I'd expect, though. That seems really odd, given that selectWoo was designed to fix the a11y problems with select2 🤔
The selectWoo demo does still let you search, though, with a sequence like this:
Tab to list
Hit enter
Start typing
There's no visual affordance that you can/should start typing, though, which seems odd. Our instance doesn't work with a sequence like that.
It may be better to just replace it with something that was designed to be accessible though, like alphagov/accessible-autocomplete. I'll try that out.
Swag
linktab
one more time, which will take you to#select2-wp20-locale-switcher-container
enter
to open the menuarrowup
/arrowdown
to move between themshift-tab
to go to the search field, and it will close the list and take you back to#select2-wp20-locale-switcher-container
instead of moving the focus to the searchinput
.The text was updated successfully, but these errors were encountered: