microsoft / microsoft/terminal

[Settings]: In Scan mode, Screen Reader focus is going unnecessary on 'Button text' inside Add new a profile page.

Open
#12,013 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A11yCO A11ySev3 A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal Issue-Bug Priority-3 Product-Terminal WindowsTerminal_Win32
Dominant language
C++
Stars
105k
Forks
9.6k
Avg merge
3d 17h
Merged PRs (30d)
29

Description

Windows Terminal version

1.12.3472.0

Windows build number

10.0.22504.1010

Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: Narrator
Tool: Accessibility Insights for Windows Version 1.1.1741.1

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Settings page using 'Ctr+,'.
  3. Open Narrator using 'Win+Ctrl+ Enter' key. Turn ON Narrator scan mode using 'Caps lock + Space' key.
  4. Navigate to 'New Empty profile' and 'Duplicate' button using up/down arrow keys and observe the issue.

User Experience:
Screen Reader users UX will not be good if Screen Reader focus is going unnecessary on 'Button text if button name info is already announced with button control.

Guideline Reference:
https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence

Attachments:
In Scan mode, Screen Reader focus is going unnecessary on 'Button text' inside Add new a profile page..zip

Expected Behavior

In Scan mode, Screen Reader focus should not go unnecessary on 'Button text' inside Add new a profile page as button information is already announced with control.

Actual Behavior

In Scan mode, Screen Reader focus is going unnecessary on 'Button text' inside Add new a profile page.
i.e. On pressing 'first' down arrow key on 'New empty profile', Screen Reader is announcing 'Create New button button'.
On pressing 2nd down arrow key Screen Reader focus goes on 'New Empty profile' text and read it.

Observation: Not able verify with NVDA Screen Reader as its browse mode does not work in app.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the Windows Terminal Settings page with Narrator Scan mode, following the listed steps and observing focus on the New Empty profile and Duplicate controls. Trace the settings UI handling for those controls and verify that Scan mode no longer focuses the separately announced button text while the button name remains announced.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
accessibility, desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.