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
VoiceOver & accessibility support #1084
Comments
+1 |
1 similar comment
+1 |
+1 |
+1 |
2 similar comments
+1 |
+1 |
With Voice over and Talkback screen readers on, user is unable to select the option from the list by double tap. |
+1 |
@liorbentov I just went over this and it seems to work with Voiceover now for the most part. May be because an update to OSX. It is a bit confusing, when you tab in it announces it as a group and you can use the arrow keys, each option is announced as the label and 'clickable'. When you tab out it just says 'collapsed, button'. Not great but better than no voiceover at all. If you have some specific bugs / improvements based on how it behaves now I can dig into it as I need it for work and must meet WCAG AA standards. |
@roborourke Have you tried it with the Voiceover on iOS? It hasn't been working for me at all in that use case. Not sure if that is a part of the standards or not. |
@roborourke voiceover on a webview in iOS is not working for me either. I am unable to select an option from the group. I have tried removing the fast click as well as preventing default behavior on touchStart. Attached is a video. Any help or insight would be great! |
Ah sorry, this was chrome on macOS. I’ll do some actually thorough testing
…On Fri, 23 Feb 2018 at 22:19, Renee Dudley ***@***.***> wrote:
@roborourke <https://github.com/roborourke> voiceover on a webview in iOS
is not working for me either. I am unable to select an option from the
group. I have tried removing the fast click as well as preventing default
behavior on touchStart. Attached is a video. Any help or insight would be
great!
https://imgur.com/a/VU2FQ
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1084 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABbeWpU9dJQV4dCvj2hLdvqOBIiQWhRks5tXzlagaJpZM4JKbmp>
.
|
@roborourke - I've done some aria research which might be of help. Several people have documented that they are unable to select when role combobox is being used. So a potential fix could be allowing the user to override the |
Can confirm that NVDA reads out each option when navigating with arrow keys on IE & Firefox. macOs voiceover is silent on arrow key navigation using any browser. |
I'm having the same issue. This content was generated by the react-select 1.2.1. Somehow VO can't read the aria-label on the div with role="option". Then I copied the the div class="Select-menu-outer" tag to jsfiddle. And it's working. https://jsfiddle.net/stonebat/w4xxas99/2/ Any one...any idea?
|
I used the valueComponent and menuRenderer options with these methods to get the focused option and selected value to be spoken by VoiceOver.
|
@techiemon, could you post an entire working example of this this code working with a react component? This could be exactly what my company needs for a project, but it's not clear from the docs how the params object works. |
@EnshaednHiker Look for the component you want to replace and view the code example (small little toggle button, not immediately obvious). They all get |
Also, if anyone could outline what exactly is needed to make this screen reader accessible, I'd love to make a PR. Is @techiemon 's solution adequate? |
Not really, it's more a workaround than the proper solution.
But then when using autocomplete and AJAX loading, it becomes a little harder. Personally, if you must support accessibility AA or AAA, I'd recommend going with a native (you can style the trigger, by putting it into opacity: 0 and decorating the background / parent container) |
Hello - In an effort to sustain the We understand this might be inconvenient but in the best interest of supporting the broader community we have to direct our efforts towards the current major version. If you aren't using the latest version of However, if you feel this issue is still relevant and you'd like us to review it - please leave a comment and we'll do our best to get back to you! |
Hey,
I have to say that I love this component and use it often.
However, the accessibility support isn't completed - It doesn't support Screen reader (for my knowledge)
I'm using Mac's VoiceOver, and when i'm navigating between the options with the keyboard, I expect to hear the option text (or whatever value I can pass), but nothing happens.
Would love if the component will support this feature.
The text was updated successfully, but these errors were encountered: