Screenreader has weird behavior when it comes to a specific autosuggest box compared to Chrome
Categories
(Core :: Disability Access APIs, enhancement)
Tracking
()
People
(Reporter: Josboele, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0
Steps to reproduce:
I'm testing the Accessibility of an input field with an autosuggest. I'm noticing different behavior on Firefox (in combination with NVDA) compared to Chrome with NVDA. Firefox doesn't seem to be able to read the suggestions compared to Chrome. I've tried looking up if they're using an aria-attribute which isn't supported. But I haven't been able tofind it.
Steps to produce (with NVDA activated):
- Go to https://www.ziggo.nl/klantenservice/uefa/service
- Go to the bottom of the page where you see an inputfield with the name "Waar kunnen we je mee helpen?" under de heading "Nog niet gevonden wat je zocht?"
- Fill in some text to get a list of suggestions. For example fill in "Voet".
- With NVDA active, I use the arrowkeys to browse through the suggestions.
It may be possible that this is an NVDA bug, but due to it working perfectly fine on Chromium-based browser. I think it is a Firefox issue.
Actual results:
What happened is that NVDA in combination with Firefox isn't able to tell the suggestions but only conveys the words "list highlighted [highlighted start]".
Expected results:
It should convey the a suggestion like "[highlight start] voet [highlight end] bal 1 van 5"
|
||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•2 years ago
|
||
This occurs because:
- The combobox references the listbox with aria-owns, which is an old, deprecated pattern. It does not reference the listbox with aria-controls.
- The combobox does not use aria-activedescendant to focus the selected suggestion. This is a clear violation of the ARIA spec.
- Chrome seems to implicitly map aria-owns to aria-controls in this case.
- Because of point 3, NVDA applies its logic for handling selected items whose container is controlled by the focus.
Chrome and NVDA are effectively working around the violation of the ARIA spec here. Firefox isn't incorrect as such - there is nothing in the spec that says we should map aria-owns to aria-controls in this case - but I agree that it does help users with broken cases like this, so we should probably consider it.
Description
•