Closed kolaps33 closed 1 year ago
It's not a focus issue, since the input keeps focus throughout all combobox interactions. To me, this looks like a screen reader bug, though there is a workaround.
The APG example clears the aria-activedescendant
id when the right or left arrows or home/end are pressed, or when the user deletes a letter. It also resets to the top of the list when you go to arrow down again.
I don't really like the reset behavior, but we could clear the attribute value when the insertion point moves as a temporary measure. I'll also file 3rd party bugs, this seems like a fairly severe issue on the screen reader side.
Library
React Northstar / v0 (@fluentui/react-northstar)
System Info
Are you reporting Accessibility issue?
None
Reproduction
https://codesandbox.io/s/7mzpld?file=/example.tsx
Bug Description
Navigate between letters: Steps:
Actual Behavior
screen reader is not narrating letters
Expected Behavior
screen reader narrate letters which user navigate on
Delete letters: Steps:
Actual Behavior
screen reader is not narrating deleted letters
Expected Behavior
screen reader narrate letters which user deleted
Comment: It works with ARIA example: https://w3c.github.io/aria-practices/examples/combobox/combobox-autocomplete-list.html Looks like issue is when we use left/right arrow keys we need to get screen reader focus on input. The similar with backspace, in order enable screen reader to narrate deleted letters we need to have screen reader focus on input. At least this is what I observe on ARIA example that screen reader focus ring moving to input when user navigate between letters or preses backspace.
Logs
No response
Requested priority
Normal
Products/sites affected
No response
Are you willing to submit a PR to fix?
no
Validations