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
I'm a web accessibility engineer for a digital agency, and one of our clients is a Federal US agency with millions of website visitors per month. They have a few licensed implementations of Mapbox, and the ones that use the GL search feature display the following bugs and do not conform to accessibility requirements. Fixing this issue will mean our disabled users can take full advantage of Mapbox functionality, and most importantly, have a much better online experience when performing a Mapbox search.
Steps to Trigger Behavior
Enable a screen reader (I tested using VoiceOver and Safari, MacOS 14.1)
Enter a term in the search input, like "restaurant", that displays a menu of options
Hitting the Tab key selects the first item and submits the form, which is unexpected. Tab should move focus to the next interactive element.
In the search input, use the down arrow key to traverse the menu. You'll notice the following:
Focus remains on the input and does not move to the menu.
On the first press of the down arrow, selection (active style) skips the first item and moves to the second menu item.
The screen reader does not read any of the menu items aloud until a selection is made. (VoiceOver repeats the input's text value every time a new selection is made.)
Pressing the Tab key moves focus to the next interactive element and does not submit the search.
Pressing the down arrow moves focus and selection to the first item in the menu so that it's announced by a screen reader.
Subsequent up/down arrow presses move focus and selection to the previous/next item in the menu. Basically, menu behavior should replicate a standard combobox or HTML select element.
Space bar or Enter selects the focused item in the menu and submits the search.
mapbox-gl-js version: Latest
browser: All
Why we need this fixed
I'm a web accessibility engineer for a digital agency, and one of our clients is a Federal US agency with millions of website visitors per month. They have a few licensed implementations of Mapbox, and the ones that use the GL search feature display the following bugs and do not conform to accessibility requirements. Fixing this issue will mean our disabled users can take full advantage of Mapbox functionality, and most importantly, have a much better online experience when performing a Mapbox search.
Steps to Trigger Behavior
Link to Demonstration
The issues are present in this demo: https://docs.mapbox.com/mapbox-gl-js/example/mapbox-gl-geocoder-outside-the-map/
Expected Behavior
When a user enters text in the search box:
Patterns to emulate: https://www.w3.org/WAI/ARIA/apg/patterns/combobox/
Actual Behavior
When a user enters text in the search box:
The text was updated successfully, but these errors were encountered: