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.

Sign up for GitHub

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

Screen reader not reading some full keybindings #6140

Closed
vsccarl opened this issue May 5, 2016 · 3 comments
Closed

Screen reader not reading some full keybindings #6140

vsccarl opened this issue May 5, 2016 · 3 comments
Assignees
@bpasero @sbatten
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug electron Issues and items related to Electron upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded
Milestone
August 2018

Comments

@vsccarl
Copy link

vsccarl commented May 5, 2016

  • VSCode Version: 1.1.0-alpha
  • OS Version: Windows 10

Steps to Reproduce:

Prereq: Install NVDA

There are a few keybindings not being read:

  1. Right click in a file and hover over "Change All Occurances" reads as "Ctrl +" and does not read F2
  2. In the Goto menu "Go to Definition" does not read F12.
  3. In the File menu "Close Editor" reads "Ctrl +" and does not read F4
  4. In the View menu "Zoom out" reads "Ctrl +" and does not read "-"
  5. In the View menu "Split Editor" reads "Ctrl +" and does not read ""
@vsccarl vsccarl added accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues v-test labels May 5, 2016
@bpasero
Copy link
Member

bpasero commented May 6, 2016

@vsccarl are other keybindings being read fully?

@bpasero bpasero added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label May 6, 2016
@bpasero bpasero added this to the Backlog milestone May 6, 2016
@bpasero bpasero self-assigned this May 6, 2016
@vsccarl
Copy link
Author

vsccarl commented May 6, 2016

@bpasero yes, all others are being read fully.

@bpasero bpasero added the bug Issue identified by VS Code Team member as probable bug label Aug 17, 2016
@egamma egamma removed the v-test label Aug 22, 2016
@bpasero bpasero added workbench and removed workbench 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 added electron Issues and items related to Electron and removed workbench labels Nov 12, 2017
@bpasero bpasero removed this from the Backlog milestone Nov 16, 2017
@sbatten sbatten mentioned this issue May 10, 2018
Closed
@bpasero bpasero added the bug Issue identified by VS Code Team member as probable bug label Aug 17, 2018
@bpasero bpasero added this to the August 2018 milestone Aug 17, 2018
@bpasero
Copy link
Member

bpasero commented Aug 17, 2018

We will change to custom menus on Windows. For now you can set "window.titleBarStyle": "custom".

@bpasero bpasero closed this as completed Aug 17, 2018
@RMacfarlane RMacfarlane added the verified Verification succeeded label Aug 29, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bpasero bpasero

@sbatten sbatten

Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug electron Issues and items related to Electron upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded
Projects
None yet
Milestone
August 2018
Development

No branches or pull requests
5 participants
@egamma @bpasero @RMacfarlane @sbatten @vsccarl