-
Notifications
You must be signed in to change notification settings - Fork 30
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
Improve Accessibility #7
Comments
Oh, one other thing. Make it so I can move my arrows left and right to toggle or up and down when it's vertical. |
Okay
|
It should also be operable with the space bar or enter key. Regular switch toggles are just like ARIA checkboxes. Here are some tips for tri-state toggles: https://webaccessibility.withgoogle.com/unit?unit=6&lesson=14 |
Thanks @marcysutton! |
Excellent resource! On Tue, Jul 7, 2015 at 5:25 PM Kent C. Dodds notifications@github.com
|
ng-toggle is going to get some great attention here pretty quick. The On Tue, Jul 7, 2015 at 5:26 PM Tanner Linsley tannerlinsley@gmail.com
|
Woot! |
I'm hoping 2.0 can live up to expectations. I'd like to see it used on a larger scale. |
😂 |
This is pretty much not accessible at all. If you include
ngAria
, then you can tab to the UI component, but it doesn't give any indication to the user that it has focus. Things to do::focus
onng-toggle-switch
tabindex="0"
onng-toggle-switch
tabindex="-1"
on theng-model
element (ng-toggle-wrap
). (to preventngAria
from adding atabindex
)Bonus stuff:
role="checkbox"
if it's not atriToggle
and add the appropriate aria attributes: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_checkbox_rolerole="button"
if it is atriToggle
and add the appropriate aria attributes: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_button_roleThe text was updated successfully, but these errors were encountered: