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
Map flattened object nav gestures by default #15053
Comments
I like the power of a nested object nav if the structure of an app is correct, but I tried explaining how to navigate with NVDA's review cursor to multiple users and most of them have difficulty understanding why and when they need to use up/down/left/right. Same users have no issue understanding swipe gestues in mobile VoiceOver or using Narrator with capslock+arrows. So yes, I think mapping this by default is a great idea. |
What do you think about the proposed gestures? |
I suppose laptop layout gestures like "kb(laptop):NVDA+;", "kb(laptop):NVDA+'", "kb(laptop):NVDA+" are not available? |
I think the suggested gestures for desktop make more sense swapped |
Actually, they are. However for laptop, I prefer at least the shift+NVDA combination to stay consistent with the other keys.
You are right. I based them on the next/previous review mode gestures, but I think those are actually a bit weird. |
I have not strong opinion about gestures. You surely consider to keep gestures consistent, as well as to keep them as easy to use as possible. |
Link to issue number: Fixes #15053 Summary of the issue: Object navigation can be difficult to grasp for some people. It is helpful to assign the flattened object nav gestures (that are now only available on touch screen)by default. Description of user facing changes See change log items Description of development approach Added gestures to scripts in globalCommands.
Is your feature request related to a problem? Please describe.
Object navigation can be difficult to grasp for some people. It might be helpful to assign the flattened object nav gestures (that are now only available on touch screen)by default.
Describe the solution you'd like
Add the following additional gesture mappings:
Describe alternatives you've considered
Leave as is
The text was updated successfully, but these errors were encountered: