Accessibility
-
Has anyone used Quasar in a project that was required to be WCAG 2.0 compliant? I’m evaluating this framework for a project at the University of Washington and finding that keyboard operation is effectively non-existent. Specifically on the Toolbar and form widgets like Radio and Select.
The main problem with the toolbar is the lack of anchor tags but I think I can easily work around this by adding an onKeyPress event to them,
I’m not sure about the widgets. But before I start digging into the code or trying to write a bunch javascript to sit on top of the widgets, I figured I’d see if anyone else has gone down this road.
Ideally, I’d like to see the Quasar components support keyboard operations without needing extra coding and would be willing to help in that effort if possible.
-
Big improvements on v0.14 which is near the corner, which handles keyboard operations too