vscode: I can no longer access terminal accessibility buffer with orca
Type: Bug
CC: @meganrogge CC: @isidorn Today I updated the VScode insiders version and noticed that it is no longer possible to navigate with arrows in the terminal accessibility buffer.
I create a new terminal, type any command, press shift+tab and try to use the arrow keys to read the result of the command. Nothing is read by orca, no matter what keys I use. I also tested disabling all extensions and the result was the same.
VS Code version: Code - Insiders 1.76.0-insider (c9e3ef865539061b5602c6b9ac6030332aa1ce70, 2023-02-06T05:24:21.999Z) OS version: Linux x64 6.1.9-200.fc37.x86_64 Modes: Sandboxed: Yes
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i5-8250U CPU @ 1.60GHz (8 x 3000) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: disabled_software video_encode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off |
| Load (avg) | 1, 1, 1 |
| Memory (System) | 15.27GB (10.91GB free) |
| Process Argv | -n --crash-reporter-id bc02adbd-6c3a-44b8-af92-55103a608af7 |
| Screen Reader | yes |
| VM | 0% |
| DESKTOP_SESSION | gnome-xorg |
| XDG_CURRENT_DESKTOP | GNOME |
| XDG_SESSION_DESKTOP | gnome-xorg |
| XDG_SESSION_TYPE | x11 |
Extensions (37)
| Extension | Author (truncated) | Version |
|---|---|---|
| doxdocgen | csc | 1.4.0 |
| vscode-markdownlint | Dav | 0.49.0 |
| vscode-chatgpt | gen | 3.5.5 |
| rest-client | hum | 0.25.1 |
| better-cpp-syntax | jef | 1.17.2 |
| azure-pipelines | ms- | 1.208.0 |
| vscode-docker | ms- | 1.23.3 |
| csharp | ms- | 1.25.4 |
| vscode-kubernetes-tools | ms- | 1.3.11 |
| remote-containers | ms- | 0.276.0 |
| remote-ssh | ms- | 0.97.2023020215 |
| remote-ssh-edit | ms- | 0.84.0 |
| azure-account | ms- | 0.11.3 |
| cmake-tools | ms- | 1.13.45 |
| cpptools | ms- | 1.14.1 |
| cpptools-extension-pack | ms- | 1.3.0 |
| makefile-tools | ms- | 0.6.0 |
| powershell-preview | ms- | 2023.2.0 |
| remote-explorer | ms- | 0.2.0 |
| vsliveshare | ms- | 1.0.5828 |
| fabric8-analytics | red | 0.3.6 |
| java | red | 1.15.2023020403 |
| vscode-xml | red | 0.25.2023020103 |
| vscode-yaml | red | 1.11.0 |
| sonarlint-vscode | Son | 3.14.0 |
| cmake | twx | 0.0.17 |
| intellicode-api-usage-examples | Vis | 0.2.7 |
| vscodeintellicode | Vis | 1.2.30 |
| vscode-boot-dev-pack | vmw | 0.2.1 |
| vscode-spring-boot | vmw | 1.44.0 |
| vscode-java-debug | vsc | 0.48.0 |
| vscode-java-dependency | vsc | 0.21.2023013100 |
| vscode-java-pack | vsc | 0.25.2022112900 |
| vscode-java-test | vsc | 0.37.2023013002 |
| vscode-maven | vsc | 0.40.2023020103 |
| vscode-spring-boot-dashboard | vsc | 0.10.1 |
| vscode-spring-initializr | vsc | 0.11.2 |
(1 theme extensions excluded)
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256198
vstes627cf:30244335
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30404738
cppdebug:30492333
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30618038
pylantcb52:30590116
pyindex848:30611229
nodejswelcome1:30587009
pyind779:30611226
pythonsymbol12:30651887
hidelangstatbar:30657380
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 17 (10 by maintainers)
Commits related to this issue
- fix #173532 — committed to microsoft/vscode by meganrogge a year ago
Yes, it is working perfectly.
@jooyoungseo thank you so much for that helpful info.
the
.xterm-accessibility-treewas removed with https://github.com/microsoft/vscode/pull/173322 . @jvesouza could you pls test in OSS off of main with Orca to see if it’s fixed?@meganrogge Under
.xterm-accessibility-tree, each listitem is assigned tabindex “-1”. My hunch is that this interrupts terminal buffer document role tabindex. Why don’t we try removing the listitem’s tabindex attribute?Let me chime in. @meganrogge and @Tyriar – Currently, “document” role does not force some screen readers’ (e.g., JAWS, Narrator, and ORCA) to switch on virtual cursor automatically. NVDA and VoiceOver work properly though. Interestingly, JAWS and ORCA work when tabindex=“0” is assigned to the div where “document” role resides. I can take a deep look when I have more time later.
@meganrogge we should get an orca setup to test this out. It would be unfortunate, but maybe
'auto'in the content editable setting needs to also takeisLinuxinto account?