-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Changed Shortcut format for better accessibility #2465
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
Conversation
🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You will need to run the command |
@lindapaiste Decresing the font size might be not be a good idea as on a bigger screen its hard to see unless u look closely, in my opinion. Here are some screenshots where I decresed it to So I went with the increase in width of the dropdown option. But if we increase it just by value then there's too much whitespace in the "Help" menu. So instead I utilized the flex property so that the dropdown menu size is now dynamically set according to the options. I would like to hear your opinion about this. |
This is exactly what I came here looking for. The screenshots look good---I hope it's caught up and makes it to production! Whenever I need to refamiliarize myself with a shortcut, I just guess at what the carat vs fat arrow mean...and the fat arrow is on the keyboard I'm using right now! 😅 (Good example of a momentary/transient accessibility issue....) I did follow the link to Sublime Text, only to find even more mysterious symbols, (rather than a legend for those used in the web editor).... If the length of shortcuts were a concern, just spelling out "Ctrl" would probably be sufficiently disambiguating for me, personally. A legend might also suffice, (e.g., on hover and/or on the Keyboard Shortcuts pop-up)---it's only for occasional reference after all--but @Sheikh-JamirAlam 's solution above seems the most direct and helpful, (esp. the later versions, ensuring both legible font size and adequate space between the menu option and the shortcut). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much for your work on this! I think a few more UI adjustments could probably be made, but I think it's overall good for now and can be made down the line, so I'm going to get this in!
Fixes #2355
Changes:
Removed the symbols used in shortcuts for windows users to "Ctrl + Shift" format so that every user can understand.
I have verified that this pull request:
npm run lint
)npm run test
)develop
branch.Fixes #123