-
Notifications
You must be signed in to change notification settings - Fork 0
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
Tables cannot be explored with keyboard navigation #37
Comments
Limitations of the built-in component provided by Vue are revealed on the demo page: https://v2.vuetifyjs.com/en/components/data-tables/ You can see how checkboxes are not focusable at all. You can also see how action buttons are focusable by default. As for clicking on a row, I recommendation is that we deprecate the ability to click on the row itself in favor of having an new action button that does the same thing. We have had several users attempt to click the checkbox or the action buttons instead of the row itself, so this could eliminate some confusion. As for selecting a row (like in Edit Lab Details), I do not know the best way forward. Shuan and I decided to deprecate the table on the Dashboard page with the goal of making the Dashboard page fully keyboard accessible. |
Yeah, I don't even remember why we have checkboxes for Labs in the first place! I like the idea of having action buttons for the various modes, "Edit", "View", "Delete", etc. |
Also, yeah the assets table has always seemed a little out of place on the dashboard. |
Haha, yeah. We probably should have removed it when we took out the metrics summary. One day we'll have a cool AI dashboard B) |
Oh also, @ho-yi-shiuan, a couple things:
|
For 2, actually the whole table isn't able to be selected, although it has a tabindex, I can't select it with tab. |
Expected behavior
Table rows and table rows' buttons are navigable by pressing tab on a keyboard.
Actual behavior
Inconsistent:
How to reproduce
On any page with a table, try to navigate the table with a keyboard only.
Thank you @ho-yi-shiuan for bringing this up!
The text was updated successfully, but these errors were encountered: