You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Windows Terminal]: Screen reader is just announcing a single character information while navigating using ctrl + left/right arrow keys in mark mode. #17892
Test Environment:
OS: Windows 11 Version Dev (OS Build 27695.1000)
App: Windows Terminal Preview
Screen Reader: Narrator
Steps to reproduce
Repro steps :
1.Open Windows Terminal.
2.Navigate to the editor.
3.Turn on Narrator by pressing 'Ctrl + Windows + Enter' keys.
4.Now turn on mark mode by pressing 'Ctrl + Shift + M' keys.
5. Now navigate among words using 'Ctrl + Left/Right' keys.
6.Observe the screen reader narration here.
Observation using NVDA and JAWS screen reader:
Same issue repro with NVDA and JAWS screen reader also.
User Experience
Users who rely on screen reader may not get the info properly while navigating in mark mode.
Screen reader should narrate complete word information while navigating using ctrl + left/right arrow keys in mark mode.
Actual Behavior
Screen reader is just announcing a single character information while navigating using ctrl + left/right arrow keys in mark mode.
For example:
For word "Microsoft", screen reader is just announcing as 'M selected' when we navigate using 'Ctrl + Left' arrow key and announces as 't selected' using 'Ctrl + Right' arrow.
This is by design. Pressing Ctrl+Left/Right moves you to the previous/next word respectively. You're just moving the cursor around, which is why the resulting announcement by the screen reader is what is selected (in the case above, "M"). If you want to expand the selection instead of just moving the cursor, you'll need to hold the Shift key.
But should we perhaps narrate an entire word when the cursor position moves by more than 1 cell? That's what seems to happen when using Word at least. I'm not entirely sure how to implement this though.
Carlos Zamora (@carlos-zamora),
This issue is logged from the feedback of Adam Samec. As mentioned in the mail we should be able to navigate among the words using 'Ctrl + Left/Right' arrow keys.
Screen reader is just narrating as selected with single character information instead of narrating the complete word information.
I suspect that fixing both of those issues may fix this one inadvertently. Totally based on a hunch, but I wonder if screen readers behave differently when the cursor moves as a degenerate range (like, maybe they automatically read out the current word since there's no selected text).
Tried looking at Word under accevent but all I got was TextSelectionChanged events, which means that the screen reader has special logic to handle that (pretty standard) then calls the UIA APIs off of the text provider.
Carlos Zamora (@carlos-zamora) This bug is impacting Windows Terminal product compliance and making it D. Any expected/tentative ETA by when this issue can be fixed?
Activity
carlos-zamora commentedon Sep 10, 2024
This is by design. Pressing Ctrl+Left/Right moves you to the previous/next word respectively. You're just moving the cursor around, which is why the resulting announcement by the screen reader is what is selected (in the case above, "M"). If you want to expand the selection instead of just moving the cursor, you'll need to hold the Shift key.
Closing as by design.
lhecker commentedon Sep 10, 2024
But should we perhaps narrate an entire word when the cursor position moves by more than 1 cell? That's what seems to happen when using Word at least. I'm not entirely sure how to implement this though.
Saurabh220304 commentedon Sep 11, 2024
Carlos Zamora (@carlos-zamora),
This issue is logged from the feedback of Adam Samec. As mentioned in the mail we should be able to navigate among the words using 'Ctrl + Left/Right' arrow keys.
Screen reader is just narrating as selected with single character information instead of narrating the complete word information.
carlos-zamora commentedon Sep 11, 2024
I see. Ok, reopening.
Related issues:
I suspect that fixing both of those issues may fix this one inadvertently. Totally based on a hunch, but I wonder if screen readers behave differently when the cursor moves as a degenerate range (like, maybe they automatically read out the current word since there's no selected text).
Tried looking at Word under accevent but all I got was TextSelectionChanged events, which means that the screen reader has special logic to handle that (pretty standard) then calls the UIA APIs off of the text provider.
Priyanka-Chauhan123 commentedon Jan 22, 2025
Carlos Zamora (@carlos-zamora) This bug is impacting Windows Terminal product compliance and making it D. Any expected/tentative ETA by when this issue can be fixed?
Make selection an exclusive range (microsoft#18106)