Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Terminal output div container should be more accessible for screen readers

See original GitHub issue

CC @isidorn

System Info

Version: 1.46.0-insider (system setup)
Commit: cd41dd1f6065db76c77c6e2f659bb50e6f558dec
Date: 2020-05-29T05:51:32.662Z
Electron: 7.3.0
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

Steps to Reproduce:

With either NVDA or JAWS loaded, type any commands in terminal (Ctrl+`) input area.
Press Shift+Tab two times from the terminal input to focus in terminal output list view.
The terminal output list is reachable via tab key thanks to tabindex = "0" attribute; however, screen readers (both NVDA and JAWS) do not read anything with arrow keys unless users manually switch on browse mode.
The additional problem can be found with very long terminal outputs that require scroll behavior. Screen reader users have to switch back to forms mode to arrow up/down to scroll through the output history (while not being read any current line) and again, turn back to browse mode to check the results.

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

Suggested Solutions

Currently, the terminal output <div> container denoted with class = "xterm-accessibility-tree" has role = "list".

As a blind developer myself, I am requesting the following for accessibility improvements for screen readers.

Please change the value of role attribute from "list" to "document" so that screen reader users can navigate the terminal output via arrow keys using browse mode.
Please adjust the tabindex value of this terminal output container in the way that screen reader users can quickly Shift+Tab from terminal input area. In other words, pressing tab key from terminal output area should go to terminal input area; pressing Shift+Tab key from terminal input goes to terminal output area denoted with role = "document" div.
Ideally, it would be great if the terminal output can be also included in the F6-keycycle.