Skip to content

Accessibility issue with CTRL+k, CTRL+i moving the cursor on top of file #251890

Open
@dstpierre

Description

@dstpierre

Type: Bug

Inspecting something with CTRL+k, CTRL+i to simulate a mouse pop-over is very useful when using a screen reader (no mouse).

Since this last version after hitting ESC to return to code (out of the tooltip) the editing cursor returns to top of file at line 1.

VS Code version: Code 1.101.0 (dfaf441, 2025-06-11T15:00:50.123Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 6.6.87.2-microsoft-standard-WSL2

System Info
Item Value
CPUs Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz (4 x 3312)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
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_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 15.89GB (8.48GB free)
Process Argv --folder-uri=vscode-remote://wsl+Ubuntu-22.04/home/dstpierre/src/qlix --remote=wsl+Ubuntu-22.04 --crash-reporter-id 7ffcd57e-272c-4083-8aeb-17ee48dd8ae6
Screen Reader yes
VM 0%
Item Value
Remote WSL: Ubuntu-22.04
OS Linux x64 6.6.87.2-microsoft-standard-WSL2
CPUs Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz (4 x 0)
Memory (System) 7.70GB (6.51GB free)
VM 0%
Extensions (13)
Extension Author (truncated) Version
remote-wsl ms- 0.99.0
ruff cha 2025.24.0
elm-ls-vscode elm 2.8.0
prettier-vscode esb 11.0.0
vscode-pull-request-github Git 0.110.0
go gol 0.46.1
vscode-test-explorer hbe 2.22.1
debugpy ms- 2025.8.0
python ms- 2025.8.0
vscode-pylance ms- 2025.6.1
test-adapter-converter ms- 0.2.1
rust-analyzer rus 0.3.2500
volar Vue 2.2.10
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
pythonrstrctxt:31112756
nativeloc2:31192216
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
hdaa2157:31222309
copilot_t_ci:31222730
e5gg6876:31282496
pythoneinst12:31285622
bgtreat:31268568
4gafe986:31271826
c7cif404:31314491
e77a2192:31326280
pythonpulldiag:31325930
996jf627:31283433
pythonrdcb7cf:31303019
usemplatestapi:31297334
0aa6g176:31307128
7bj51361:31289155
747dc170:31275177
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
pylancequickfixf:31329273
he899328:31327032
useunpkg:31331645
1292j425:31329156

Metadata

Metadata

Labels

accessibilityKeyboard, mouse, ARIA, vision, screen readers (non-specific) issuesbugIssue identified by VS Code Team member as probable bugconfirmedIssue has been confirmed by VS Code Team memberimportantIssue identified as high-priorityregressionSomething that used to work is now broken

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions