Keyboard and general accessibility

[patrickhlauke]

It would be nice if the components also worked for keyboard users (also providing the focus styling defined in the Material Design guidelines) and assistive technologies...

[OscarGodson]

http://www.google.com/design/spec/usability/accessibility.html

[hai-cea]

Yep - totally agree. Working on cleaning up components to account for this. This is done for Icon Buttons and the other components will follow.

Check out http://material-ui.com/ and hit the tab key. :)

[gavrochelegnou]

It would be great to implement aria roles on every widget.
For example on the dialog :
http://www.nczonline.net/blog/2013/02/12/making-an-accessible-dialog-box/
For dropdown menu :
http://staff.washington.edu/tft/tests/menus/html5/
Many examples :
http://heydonworks.com/practical_aria_examples/

[marcysutton]

I would recommend auditing your project with the Chrome Accessibility Developer Tools and reading up on accessibility best practices, there are many issues beyond just keyboard tabbing: https://chrome.google.com/webstore/detail/accessibility-developer-t/fpkknkljclfencbdbgkenhalefipecmb?hl=en

[hai-cea]

Thanks @marcysutton - I'll check it out.

[matthewoates]

https://github.com/rackt/react-a11y should be much more friendly @hai-cea. https://www.youtube.com/watch?v=z5e7kWSHWTg&t=644

[mmrtnz]

@matthewoates Thanks for showing this to us :)

[vujita]

I use a chrome extension that helps detect accessibility. I really want to use this lib, but I need it to be able to pass this tools checks at least