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

Jump to bottom

NVDA reports "Program Manager" when using read window title command (NVDA+T) on the Desktop #4344

Closed
nvaccessAuto opened this issue Jul 30, 2014 · 4 comments
Closed

NVDA reports "Program Manager" when using read window title command (NVDA+T) on the Desktop #4344

nvaccessAuto opened this issue Jul 30, 2014 · 4 comments
Labels
bug close/duplicate

Comments

@nvaccessAuto
Copy link

Reported by brandon15 on 2014-07-30 17:41
When you go to the desktop and move around the icons, and you check the window title with NVDA+T, NVDA reports Program Manager.
Following are the steps to reproduce this problem:

  1. Press Windows+M to go to the Desktop. NVDA should say "Desktop list."
  2. Press NVDA+T to read the window title. NVDA will say "Program manager."
    Instead, I think NVDA should say "Desktop" as this seems like a better name for this in my opinion.
    This is not a huge problem, but I was just wondering if it could be corrected when you have time if you don't mind please.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2014-07-30 22:49
Believe it or not, this is actually what Windows is exposing as the name for that window for accessibility purposes. I agree it's rather odd.

@nvaccessAuto
Copy link
Author

Comment 2 by blindbhavya on 2014-08-02 16:18
Hi.
When you press Windows + D to go to the Desktop and press NVDA + T, NVDA says Explorer. NVDA reports the Desktop as Explorer in some other cases as well but for now I am mentioning only this situation.
However, when you press Windows + M, somehow NVDA says Program manager.
I am going to file a ticket for this, so do comment on it. Number should mostly be 4353.

@bhavyashah
Copy link

@jcsteh If NVDA is correctly reporting whatever Windows is exposing, I reckon it is okay to leave the current behaviour as it is, particularly because users are already familiar with this. Still, if you believe that this might be a quickfix/goodfornewdevs which may not confuse existing users, that would be equally fine by me. Feel free to triage accordingly.

@jcsteh
Copy link
Contributor

jcsteh commented Aug 14, 2017

Closing as duplicate of #4353, since that issue has more detail and the same fix should be applied to cover both cases.

@jcsteh jcsteh closed this as completed Aug 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug close/duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jcsteh @nvaccessAuto @bhavyashah