You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
I'm sure this is already planned for accessibility/etc., but as a "keyboard-preferred" user, I just wanted to log the request to be able to fully navigate the UI via the keyboard. For my use-cases (and many of users), this would dramatically improve the usability. As a data point, this is actually one area where we "won" over some users to F12, because our tools were much more keyboard friendly than Chrome's were at one point. They've improved this significantly, so I'm not suggesting that it's a differentiating point, but it became very clear to us from working with many devs that keyboard nav is a not just a valuable feature, but a "table stakes" experience that is expected by many users.
The text was updated successfully, but these errors were encountered:
I'm sure this is already planned for accessibility/etc., but as a "keyboard-preferred" user, I just wanted to log the request to be able to fully navigate the UI via the keyboard. For my use-cases (and many of users), this would dramatically improve the usability. As a data point, this is actually one area where we "won" over some users to F12, because our tools were much more keyboard friendly than Chrome's were at one point. They've improved this significantly, so I'm not suggesting that it's a differentiating point, but it became very clear to us from working with many devs that keyboard nav is a not just a valuable feature, but a "table stakes" experience that is expected by many users.
The text was updated successfully, but these errors were encountered: