New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Examples don't work in VoiceOver #1539
Comments
Indeed, there seems to be an issue with VO and Safari, for useCombobox. Unfortunately, the same issue occurs on the ARIA example as well. Maybe we should check the Apple VO issues. Yes, Spectrum uses a different pattern, but the activedescendant should work as well, according to ARIA. I saw that you mentioned the issue is about |
It's been a problem with Safari for a while. That's why I don't know what the resolution is besides changing the strategy for highlighting. It makes things really difficult when Safari doesn't follow the spec. Here's another bug report. |
downshift
version: 8.0.0, 7.x, likely othersRelevant code or config
useSelect examples
What you did:
What happened:
VoiceOver does not seem to either recognize or correctly interpret the
aria-activedescendant
attribute, resulting in no readout when cylcing through the different options.Problem description:
Suggested solution:
I'm afraid I don't have a simple solution, but I wanted you all to be aware and find out if you have any ideas. We've been using Downshift in a combobox pattern (with a text field) using v3.x for several years, and VoiceOver read out the options. Nowadays we have to use the a11y-message feature to fill in the missing VO messaging, but it's proven very unreliable.
A couple months ago, I read through this article about
active-descendant
and focus management, and it seemed like the more reliable strategy would be to actively move focus between the options in the listbox. One library that seems to have done that effectively is Adobe Spectrum.That's all. I think something fundamental would have to change in how Downshift works to support that focus paradigm, but maybe ya'll have already thought about that for v9. I heard that the a11y-message system is going away.
The text was updated successfully, but these errors were encountered: