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

Terminal: NVDA does not announce any information when a terminal gets added or deleted #52304

Closed
AccessibilityTestingTeam-TCS opened this issue Jun 19, 2018 · 11 comments · Fixed by #60632
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 macos Issues with VS Code on MAC/OS X terminal Integrated terminal issues verified Verification succeeded
Milestone

Comments

@AccessibilityTestingTeam-TCS
Copy link

AccessibilityTestingTeam-TCS commented Jun 19, 2018

Environment Details:
VSCode Version : 1.24.0
OS Version : Win10
Mac OS Version:HighSierra10.13.5

Additional Details:
MAS Violated: MAS1.3.1
ScreenReader Version: NVDA2018.2

Repro Steps:

  1. Launch VS Code while NVDA/VoiceOver is ON.
  2. Go to View menu and Select Integrated Terminal.
  3. Tab till Add Terminal button(+) or delete terminal and press enter

Actual:
NVDA does not announce any information when a new terminal gets added or deleted. When a new terminal opens, it also gets added to combobox and same happens when we delete any terminal. Issue also found with VoiceOver.

Expected:
NVDA should announce some information when any new terminal gets added or deleted and also the current terminal where user is working.

Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx

User Impact:
User will not get the proper information about new terminals.

MAS Reference
https://microsoft.sharepoint.com/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}

Attachment for Reference:
A11y VSCode Terminal NVDA Add Delete Terminal.pptx

Does this issue occur when all extensions are disabled?: Yes

@vscodebot vscodebot bot added the terminal Integrated terminal issues label Jun 19, 2018
@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues labels Jun 19, 2018
@isidorn
Copy link
Contributor

isidorn commented Jul 4, 2018

This feel like the terminal service could simply do aria.alert whenever a new terminal is opened. Similar to how we do in debug lang. Feels like low hanging fruit, assigning to july

@isidorn isidorn added this to the July 2018 milestone Jul 4, 2018
@isidorn isidorn changed the title [Accessibility]A11y_VSCode_ViewIntegratedTerminal_ScreenReader: NVDA does not announce any information when a new terminal gets added or deleted. Terminal: NVDA does not announce any information when a terminal gets added or deleted Jul 4, 2018
@Tyriar Tyriar modified the milestones: July 2018, August 2018 Jul 30, 2018
@Tyriar Tyriar modified the milestones: August 2018, September 2018 Aug 27, 2018
@alexr00
Copy link
Member

alexr00 commented Sep 12, 2018

It doesn't look like this is as simple as adding aria.alert whenever a terminal is opened or closed. The alert gets interrupted by whatever has focus next. On terminal start, this is the text in the terminal. On terminal stop this is whatever document is open or the main canvas.

@Tyriar
Copy link
Member

Tyriar commented Sep 12, 2018

@AccessibilityTestingTeam-TCS what is the ideal behavior given the number of announcements that can follow? Would it be best to say "Terminal created, terminal focused, c colon backslash blah blah"?

@Tyriar Tyriar modified the milestones: September 2018, Backlog Sep 14, 2018
@Tyriar Tyriar modified the milestones: September 2018, October 2018 Sep 24, 2018
@Tyriar
Copy link
Member

Tyriar commented Sep 28, 2018

The answer to this is that we don't need to announce added or deleted terminals but rather announce the focused terminal only. If the active terminal dies we don't need to announce it, just announce the other terminal or editor that's focused afterwards.

@chrmarti chrmarti added the a11ymas Issue from accessibility team label Oct 2, 2018
@Tyriar
Copy link
Member

Tyriar commented Oct 8, 2018

@alexr00 do you have enough info to do this for October?

@alexr00
Copy link
Member

alexr00 commented Oct 10, 2018

@Tyriar, the current behavior is that the screen reader starts reading the contents of the next item to be focused. Instead, if the terminal has focus and then dies we should announce what gained focus and not the contents of the thing that gained focus?

@Tyriar
Copy link
Member

Tyriar commented Oct 10, 2018

@alexr00 example scenario as I understand it:

  1. Toggle+focus terminal, "Terminal 1, ~/dev >"
  2. Hide terminal, "somefile, blah" (whatever the editor announces)
  3. Toggle+focus terminal, "Terminal 1" (~/dev > was already covered in 1)
  4. Kill terminal, "somefile, blah" (whatever the editor announces)

@alexr00
Copy link
Member

alexr00 commented Oct 11, 2018

I see. So the change here is to announce "Terminal " every time the terminal gains focus. The cwd is already read after the terminal is focused, though not immediately.

@alexr00
Copy link
Member

alexr00 commented Oct 11, 2018

@Tyriar, what about when the terminal is split? Just announce the terminal number again?

@Tyriar
Copy link
Member

Tyriar commented Oct 11, 2018

@alexr00 yes, yes 😃

alexr00 added a commit that referenced this issue Oct 17, 2018
Accounce terminal number every time the terminal is focused.

Fixes #52304
@chrmarti chrmarti added the verified Verification succeeded label Nov 1, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 1, 2018
@isidorn isidorn added macos Issues with VS Code on MAC/OS X windows VS Code on Windows issues and removed windows VS Code on Windows issues labels 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 macos Issues with VS Code on MAC/OS X terminal Integrated terminal issues verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants