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

ctrl+NVDA+f1 Speech Order #7338

Closed
dan1982code opened this issue Jun 28, 2017 · 1 comment
Closed

ctrl+NVDA+f1 Speech Order #7338

dan1982code opened this issue Jun 28, 2017 · 1 comment
Labels
Milestone

Comments

@dan1982code
Copy link

@dan1982code dan1982code commented Jun 28, 2017

Hitting ctrl+NVDA+f1, we get something like
Currently running application is firefox.exe and currently loaded module is firefox

Could we instead consider:
firefox.exe is currently running. firefox module is loaded.

This gets us the information that we want right away. I have no UI training/expertise but it seems to make sense that the part of a message that varies should be spoken first. e.g. when we select text, we hear "hello selected", rather than "selected hello", because we know that we're selecting text, so the part that varies comes first and is the actual text selected.

@jcsteh
Copy link
Contributor

@jcsteh jcsteh commented Jun 29, 2017

What you suggest makes sense. However, this command isn't documented anywhere and is more intended for developers, since the user visible name of the application (what any other user would see) is available with NVDA+t. Therefore, assigning priority of p4.

@jcsteh jcsteh added the p4 label Jun 29, 2017
lukaszgo1 added a commit to lukaszgo1/nvda that referenced this issue Nov 7, 2018
@nvaccessAuto nvaccessAuto added this to the 2019.2 milestone May 10, 2019
@nvaccessAuto nvaccessAuto added this to the 2019.2 milestone May 10, 2019
feerrenrut added a commit that referenced this issue May 10, 2019
…anner. (PR #8927)

The command is triggered with `CTRL+NVDA+F1`.

The module name is now presented first, then the executable name with the goal of hearing the relevant information as early as possible.

Closes #7338
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.

3 participants