Skip to content

[Settings> Add new profile]: Confirmation message is not announced by Screen Reader when user create a new profile and duplicate the profile. #12038

Open

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

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Settings page using 'Ctr+,'.
  3. Open Narrator using 'Win + Ctrl + Enter' keys.
  4. Activate 'Add a new profile' tab, then activate 'New Empty profile' and 'Duplicate' button.
  5. Observe the issue.

User Experience:
Screen Reader users UX will not be good if there will not be able to know whether the action is performed successfully or not.

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

Attachments:
Confirmation message is not announced by Screen Reader when user create a new profile and Duplicate the profile..zip

Expected Behavior

Confirmation message should be announced by Screen Reader when user create a new profile and duplicate the profile.
i.e. When New profile created successfully, Screen Reader should 'profile name created successfully' and When user duplicated a profile Screen Reader should announce 'profile name created successfully'.

Actual Behavior

Confirmation message is not announced by Screen Reader when user create a new profile and duplicate the profile.

Observation: Issue repro with NVDA and JAWS Screen Reader.

Activity

  1. ghost added
    Issue-BugIt either shouldn't be doing this or needs an investigation.
    on Dec 27, 2021
  2. ghost added on Dec 27, 2021
  3. ghost added
    HCL-E+DAccessibility tracking
    on Dec 27, 2021
  4. ghost added
    A11yWCAGAccessibility tracking
    on Dec 27, 2021
  5. ghost added
    A11yCOAccessibility tracking
    on Dec 27, 2021
  6. ghost added
    A11ySev3Accessibility tracking
    on Dec 27, 2021
  7. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Dec 27, 2021
  8. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Dec 27, 2021
  9. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Dec 27, 2021
  10. added this to the 22H2 milestone on Jan 3, 2022
  11. removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Jan 26, 2022
  12. carlos-zamora commented on Jun 28, 2022

    @carlos-zamora

    Since we can't fail to create a new profile, this should be pretty easy. Just after invoking the button, send a notification event saying "profile created successfully".

  13. ghost added
    In-PRThis issue has a related PR
    on Jul 22, 2022
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

    A11yCOAccessibility trackingA11ySev3Accessibility 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.Priority-3A description (P3)Product-TerminalThe new Windows Terminal.WindowsTerminal_Win32

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions