Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility: Ctrl+Right in accessibility mode (CursorWordAccessibilityRight) should jump to the beginning of next word, rather than the end #83449

mltony opened this issue Oct 28, 2019 · 1 comment · Fixed by #83450


Copy link

@mltony mltony commented Oct 28, 2019

Issue Type: Bug

(I have fixed this myself and will send a pull request in a minute)

Steps to reproduce:

  1. Enable accessibility mode in settings.
  2. Open a new document and type:
Hello world.
  1. Go to the beginning and press Ctrl+Right.

Expected behavior:
Cursor should jump to the letter w - that is the beginning of the second word. This behavior would be consistent with word navigation in most other Windows programs, e.g. notepad, MS Word, Visual Studio - just to name a few.

Actual behavior:
Cursor jumps to the space immediately after the first word, and the screenreader announces "Hello".

The biggest problem with this behavior is that screenreader users would have to relearn how they make small edits in text files. For example, if I want to delete the word "world" in my example, I would go to the beginning of the line and press Control+Right until my screenreader announces the word I'm interested in. And then, assuming that cursor at this point is at the beginning of the word, I would press delete 5 times. However, in VSCode the cursor would be at the end of the word, and I would end up deleting wrong part of the line.

VS Code version: Code - Insiders 1.40.0-insider (29ffbfe, 2019-10-25T14:03:31.497Z)
OS version: Windows_NT x64 10.0.18362

System Info
Item Value
CPUs Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2712)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 7.85GB (1.66GB free)
Process Argv
Screen Reader yes
VM 0%
Extensions: none

This comment has been minimized.

Copy link
Contributor Author

@mltony mltony commented Nov 1, 2019

FYI, I found related discussion here: #28306, but that thread is now locked.

@isidorn isidorn added this to the November 2019 milestone Nov 27, 2019
@isidorn isidorn added the bug label Nov 27, 2019
@RMacfarlane RMacfarlane added the verified label Dec 5, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
3 participants
You can’t perform that action at this time.