[Accessibility] Command history is not readable in terminal input field via Up/DownArrow

[jooyoungseo]

CC @meganrogge

Tested with NVDA and JAWS on Windows 11.

Reproducible Steps

1. Load screen reader.

2. Launch terminal.

3. Type echo hello (hit enter).

4. Type echo world (hit enter).

5. In terminal input field, press UpArrow and DownArrow to navigate command history and see if you can hear them.

• Notes: Nothing is heard. Screen reader keeps saying "blank."

Expected Behavior

Command history needs to be accessible and readable to screen reader.

System Info

Version: 1.75.0-insider (system setup)
Commit: 0a6c277
Date: 2023-01-24T05:22:55.489Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: Yes

[meganrogge]

@jooyoungseo do you know if this has ever worked in the VS Code terminal IE is a regression? Just tried in version 1.72 and doesn't work there.

[meganrogge]

As a not ideal workaround in the meantime, you can use the Run Recent Command command to go through what you've just run.

[jooyoungseo]

@meganrogge

This is not a regression, but just a long-standing unresolved issue.

Thanks for the stopgap workaround.

Tested on Windows 11:

Terminal: Run Recent Command... does not work in terminal input area

[meganrogge]

Terminal: Run recent command... should work, do you have terminal.integrated.shellIntegration.enabled?

[jooyoungseo]

@meganrogge Yes, that's already enabled by default. Does not work even via the manual execution through command palette.

[meganrogge]

@jooyoungseo sorry if this is obvious to you already, but you have to press the down arrow immediately after running that to go to the most recently run command. then pressing the down arrow again will take you to the second most recently run one. to run it, you'd press enter