Skip to content
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

Windows 10 settings: NVDA does not provide easy access to the back button #6950

Closed
PratikP1 opened this issue Mar 8, 2017 · 4 comments
Closed
Labels
Milestone

Comments

@PratikP1
Copy link

@PratikP1 PratikP1 commented Mar 8, 2017

In the Windows 10 settings app, win+i, The back button appears adjacent to the system menu and to the minimize, maximize, and close buttons. But, navigation to this button via the NVDA object navigation leads to a lot of confusion. there are multiple "Settings window" objects that appear in the object navigation. For example, two "Settings Window; settings" objects appear adjacent to each other and more. This behavior does not occur in Narrator. I've asked Microsoft to assign a keyboard command to Back and Home buttons. But, ideally, both home and back buttons should appear in the tab order. Let me know if you want a log.
STR:

  1. Open the Settings app (windows+i).
  2. Go to one of the settings such as "updates and security."
  3. Use object nav to move up the hierarchy to the "settings window" level and move to the next and previous objects.

Test environment: Windows 10 Pro build 15048
NVDA version next-13899,af44c1d4

@jcsteh
Copy link
Contributor

@jcsteh jcsteh commented Mar 8, 2017

@jcsteh
Copy link
Contributor

@jcsteh jcsteh commented Mar 8, 2017

@PratikP1
Copy link
Author

@PratikP1 PratikP1 commented Mar 8, 2017

@JulienCochuyt
Copy link
Collaborator

@JulienCochuyt JulienCochuyt commented Jul 15, 2019

Ah. I hadn’t realized the backspace command was working there. I should have tried and known. Thank you.

As there is a Windows keyboard shortcut for this functionality, maybe could we close this issue?
cc @feerrenrut

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants