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

[Terminal]: Screen Reader does not announce Confirmation message after actions executed successfully. #12055

Open
ghost opened this issue Dec 28, 2021 · 1 comment
Labels
A11yCO Accessibility tracking A11ySev3 Accessibility tracking A11yWCAG Accessibility tracking Area-Accessibility Issues related to accessibility HCL-E+D Accessibility tracking HCL-WindowsTerminal Accessibility tracking Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-3 A description (P3) Product-Terminal The new Windows Terminal.
Milestone

Comments

@ghost
Copy link

ghost commented Dec 28, 2021

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

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Settings page using 'Ctr+,'.
  3. Activate 'Actions' tab.
  4. Open Narrator using 'Win + Ctrl + Enter' keys.
  5. Perform all available actions present inside 'Actions' tab.
  6. Observe the issues.

User Experience:
Screen Reader users UX will not be good as they will not be able to know whether the actions performed successfully or not.

Guideline Reference:
EN 301 549 V3.2.1: 11.5.2.15 Change notification

Attachments:
Screen Reader does not announce Confirmation message after actions executed successfully..zip

Expected Behavior

Screen Reader announce Confirmation message after any actions executed successfully.
i.e. When users reset tab color, Screen Reader should announce 'Tab Color reset successfully'

Actual Behavior

Screen Reader does not announce Confirmation message after actions executed successfully. Issue repro with all available actions present inside Actions tab page.

Observation: Issue also repro with NVDA and JAWS Screen Reader.

@ghost ghost added Issue-Bug It either shouldn't be doing this or needs an investigation. Area-Accessibility Issues related to accessibility HCL-E+D Accessibility tracking A11yWCAG Accessibility tracking HCL-WindowsTerminal Accessibility tracking A11yCO Accessibility tracking A11ySev3 Accessibility tracking Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Dec 28, 2021
@zadjii-msft zadjii-msft added the Priority-3 A description (P3) label Jan 3, 2022
@zadjii-msft zadjii-msft added this to the Terminal v2.0 milestone Jan 3, 2022
@zadjii-msft zadjii-msft added the Product-Terminal The new Windows Terminal. label Jan 3, 2022
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jan 3, 2022
@zadjii-msft zadjii-msft modified the milestones: Terminal v2.0, 22H2 Jan 3, 2022
@DHowett DHowett removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Jan 26, 2022
@carlos-zamora carlos-zamora modified the milestones: 22H2, Terminal v1.16 Jun 28, 2022
@zadjii-msft zadjii-msft modified the milestones: Terminal v1.16, Backlog Aug 1, 2022
@zadjii-msft
Copy link
Member

We should compare this with VsCode. Or even something like, multipleActions. Should that announce each and every sub action that was executed? There's a lot of actions that can be bound to a lot of different places. We'd have to reconcile with when we open new tabs, panes, or do anything else that already announces itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A11yCO Accessibility tracking A11ySev3 Accessibility tracking A11yWCAG Accessibility tracking Area-Accessibility Issues related to accessibility HCL-E+D Accessibility tracking HCL-WindowsTerminal Accessibility tracking Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-3 A description (P3) Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

3 participants