Skip to content

[Windows Terminal]: Screen reader is just announcing a single character information while navigating using ctrl + left/right arrow keys in mark mode. #17892

Closed

Description

Windows Terminal version

1.22.2362.0

Windows build number

27695.1000

Other Software

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.

WCAG Reference Link:
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships

Attachment :
Screen reader is not announcing full word information while navigating via ctrl + left_right arrow keys.zip

Expected Behavior

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.

Activity

  1. added
    Issue-BugIt either shouldn't be doing this or needs an investigation.
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Sep 10, 2024
  2. carlos-zamora commented on Sep 10, 2024

    @carlos-zamora

    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.

  3. lhecker commented on Sep 10, 2024

    @lhecker
    Member

    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.

  4. Saurabh220304 commented on Sep 11, 2024

    @Saurabh220304
    Author

    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.

  5. carlos-zamora commented on Sep 11, 2024

    @carlos-zamora

    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.

  6. removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Sep 11, 2024
  7. Priyanka-Chauhan123 commented on Jan 22, 2025

    @Priyanka-Chauhan123
    Collaborator

    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?

  8. added a commit that references this issue on Jan 28, 2025
    64d4fba
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A11ySev2Accessibility trackingA11yWCAGAccessibility trackingArea-AccessibilityIssues related to accessibilityHCL-E+DAccessibility trackingHCL-WindowsTerminalAccessibility trackingIn-PRThis issue has a related PRIssue-BugIt either shouldn't be doing this or needs an investigation.Needs-Tag-FixDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.WindowsTerminal_Win32

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions