[Accessibility]: Screen readers do not read currently focused line when using Alt+F5/Alt+Shift+F5

CC @isidorn

System Info

Version: 1.73.0-insider (system setup) Commit: 3544aabd5a2b0da2cd3a6f3fa3f00759aa9d9709 Date: 2022-10-27T21:34:51.585Z Electron: 19.0.17 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Windows_NT x64 10.0.22621 Sandboxed: Yes

Reproducible Steps

1. Load screen reader (e.g., NVDA).

2. Open any diffs between two files (or PR).

3. Press Alt+F5 to go to the next diff and Alt+Shift+F5 to go to the previous diff.

4. See if screen reader reads aloud the currently focused line: it does not say anything.

Expected Behaviors

Focused line needs to be auto-announced.

[rperez030]

@isidorn @meganrogge I wonder what the right way should be to address a request like this in the context of VS Code if it moves forward. what I mean is that, by design, screen readers, or at least NVDA and JAWS, do not read changes in cursor position automatically unless the change is initiated by the user using a text navigation command, so when we press alt +F5, the cursor moves to the line in conflict. This is detected by the screen reader and the new line appears in the Braille display if there is one connected, but the screen reader does not read the line automatically. One possibility would be to auto select the line in conflict which would cause the screen reader to read. This is what Microsoft word does, for example.

[jooyoungseo]

@meganrogge – No, this is not an inadvertent regression b/c it has never worked as far as I experienced.