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

Usability: NVDA is not reciting the "Name" and "shortcut key" for the menu options present in the visual studio code appropriately. #17224

Closed
WiproPSAccTest opened this issue Dec 15, 2016 · 3 comments
Assignees
Labels
a11ymas Issue from accessibility team accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug verified Verification succeeded windows VS Code on Windows issues
Milestone

Comments

@WiproPSAccTest
Copy link

WiproPSAccTest commented Dec 15, 2016

VS Code Version: 1.6.1
OS Version:1607
Steps to Reproduce:
Prerequisite: NVDA screen reader need to open.
1.Open visual studio code.
2.Using "Alt + F", key navigate to the "File" menu option.

Expected Result:
NVDA should announce the "Name" and the "Shortcut key" for the menu options in the visual studio code.
Ex: NVDA should announce File Menu option Alt+F

Actual Result:
NVDA is not announcing the menu options appropriately.
NVDA is announcing "menu sub menu"
Note: Same issue is observed for other menu options(Edit, View, Go, Help)

User Impact:
Screen Reader user doesn't get to know that the options corresponds to which Menu bar.

inspectinformation_visualstudiocodeeditor_filemenuoption
nvda_speechviewerinformation_vscodeeditor_filemenuoption

@kieferrm kieferrm added the accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues label Dec 15, 2016
@bpasero bpasero added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Dec 16, 2016
@bpasero bpasero added this to the Backlog milestone Dec 16, 2016
@bpasero bpasero added workbench bug Issue identified by VS Code Team member as probable bug and removed bug Issue identified by VS Code Team member as probable bug labels Apr 7, 2017
@bpasero bpasero added the menu label May 26, 2017
@bpasero bpasero removed the workbench label Nov 15, 2017
@bpasero bpasero removed this from the Backlog milestone Nov 16, 2017
@bpasero
Copy link
Member

bpasero commented Jul 5, 2018

We should support this with the new custom menu implementation.

@sbatten sbatten added this to the July 2018 milestone Jul 5, 2018
@sbatten
Copy link
Member

sbatten commented Jul 5, 2018

@bpasero once we resolve the issue of focusing the menubar items themselves, this should work

@sbatten
Copy link
Member

sbatten commented Jul 10, 2018

resolved via #53924

@sbatten sbatten closed this as completed Jul 10, 2018
@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug and removed upstream Issue identified as 'upstream' component related (exists outside of VS Code) labels Jul 11, 2018
@RMacfarlane RMacfarlane added the verified Verification succeeded label Aug 1, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 24, 2018
@chrmarti chrmarti added the a11ymas Issue from accessibility team label Oct 3, 2018
@isidorn isidorn added the windows VS Code on Windows issues label Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
a11ymas Issue from accessibility team accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug verified Verification succeeded windows VS Code on Windows issues
Projects
None yet
Development

No branches or pull requests

7 participants