Test: accessibility detection improvements

[isidorn]

Refs: #162331

• Windows @hediet
• macOS @kieferrm
• Linux @roblourens

Complexity: 3
Authors: @deepak1556 @isidorn

Create Issue

---

We have improved how we auto detect if a screen reader is on when using VS Code. Now this detection should be more precise. You should verify that the detection still works fine.
If you got Windows install NVDA and JAWS and test both. If you got macOS - just use VoiceOver (Cmd+F5). If you got Linux - use Orca.

• When starting a Screen Reader with VS Code running, all VS Code windows detect this and the status bar shows "Screen Reader Detected". The editor now begins to output screen reader content to the <textarea>. This is proved by the screen reader reading the text in the editor as the editor cursor moves.
• Please also check other scenarios, such as first starting the screen reader and then launching VS Code, or reloading a window, or opening a new window, etc. In all cases, the fact that a screen reader is attached should be detected. This is important, because otherwise the editor does not output screen reader content to the <textarea> (which gives us a nice performance boost)
• Turn off screen reader. Start VS Code again. Make sure the screen reader is not detected (there is no status bar message).

[kieferrm]

This doesn't work for me at all. See #167627.

[roblourens]

It's also not working with Orca. But Daniel suggested that Orca doesn't work well with Electron anyway?

[isidorn]

@kieferrm thanks for testing, let's continue the discussion in #167627

@roblourens thanks for trying on Linux. I thought that later Chromium versions detect Orca better and would expect auto detection to work. @joanmarie might you know if latest Chrome versions still require the accessibility flag to be explicitly turned on (i.e they do not detect Orca)? Rob can you file an issue for this so we have this tracked?

fyi @meganrogge