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 any information when "Integrated Terminal" is opened. #17254

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 *duplicate Issue identified as a duplicate of another issue(s) windows VS Code on Windows issues

Comments

@WiproPSAccTest
Copy link

WiproPSAccTest commented Dec 15, 2016

VS Code Version: 1.6.1
OS Version:1607
NVDA version:-2016.2.1

Steps to Reproduce:
1.Open Visual studio code editor.
2.Using "Ctrl+`" key open the Integrated Terminals.
3.Write down the command "node " with file name and run the command.
4.Look at the output for the command

Expected result:
NVDA should recite when "Integrated Terminal" is opened and also recite for the output for the command that are executed.

Actual Result:
NVDA is not reciting when "Integrated Terminal" is opened and also not reciting the output for the executed command.

User Impact:
Screen Reader user doesn't get to know that Integrated Terminal is opened

Attachments:
nvda_speechviewerinformation_vscodeeditor_terminalservices

@kieferrm kieferrm added the accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues label Dec 16, 2016
@Tyriar
Copy link
Member

Tyriar commented Jan 2, 2017

Duplicate #8339

@Tyriar Tyriar closed this as completed Jan 2, 2017
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Jan 2, 2017
@WiproPSAccTest
Copy link
Author

@Tyriar The issue is still reproducible in both the vs code editor Insider and vs code editor 1.8.1 edition

@Tyriar
Copy link
Member

Tyriar commented Jan 18, 2017

Yes, it was reported previously in #8339

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
@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 *duplicate Issue identified as a duplicate of another issue(s) windows VS Code on Windows issues
Projects
None yet
Development

No branches or pull requests

5 participants