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

Integrated terminal isn't accessible with JAWS and NVDA #59794

Closed
auchenberg opened this Issue Oct 1, 2018 · 5 comments

Comments

Projects
None yet
5 participants
@auchenberg
Copy link
Contributor

auchenberg commented Oct 1, 2018

Report from Ryan Shugart over email

I have some unfortunate news, I just tried to use the terminal in VS Code with both JAWS and NVDA, and it doesn’t seem to be working for me. I also had Tamas who is joining our team and is a big NVDA user and more familiar with VS Code overall than me try the terminal and he couldn’t get it to read properly either. We made sure screen reader mode was turned on with alt+f1.

@goatandsheep

This comment has been minimized.

Copy link

goatandsheep commented Nov 25, 2018

This is a big issue for us as well

@Tyriar

This comment has been minimized.

Copy link
Member

Tyriar commented Jan 23, 2019

Follow ups from meeting yesterday:

  • Fix terminal when editor.accessibilitySupport is set to "auto"
  • Document terminal scroll commands in accessibility docs as it wasn’t they were available obvious
  • Figure out why buffer navigation using browse mode works in NVDA but not in JAWS (We don't support JAWS)

Tyriar added a commit that referenced this issue Jan 23, 2019

@adil-s

This comment has been minimized.

Copy link

adil-s commented Jan 26, 2019

accedently, I made terminal accessible.
in order to make terminal accessible, VS code accessibility status must be set to perminant, not auto.
I pressed alt+f1 and then ctrl + E to set the status to perminant.
since then it has been working perfect!
I tried on insider builts and usual releases too.

@Tyriar

This comment has been minimized.

Copy link
Member

Tyriar commented Jan 26, 2019

@adil-s the fix I did 3 days ago fixed this in the Insiders build, the terminal will now respect automatic screen reader detection.

@Tyriar Tyriar closed this Jan 28, 2019

@Tyriar

This comment has been minimized.

Copy link
Member

Tyriar commented Feb 1, 2019

To verify on Windows:

  • Start NVDA
  • Open VS Code, it should auto detect a screen reader
  • Verify the screen reader voices terminal input and output (eg. dir)

@mjbvz mjbvz added the verified label Feb 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment