starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

A11y_Windows Terminal_About_Screen Reader: Screen Reader is not reading the name of the dialogue box immediately when the dialogue box is opened #7495

New Issue
Closed
opened 2026-01-31 01:05:22 +00:00 by claunia · 15 comments
claunia commented 2026-01-31 01:05:22 +00:00
Owner
Copy Link

Originally created by @SpandanaPaladi on GitHub (Apr 20, 2020).

#A11y_WindowsTerminal; #WindowsTerminal; #A11yMAS; #A11yTCS; #DesktopApp; #Win10; #C+E-H; #ScreenReader; #Narrator; #NVDA; #A11ySev2; #NonBenchMark; #MAS1.3.1

Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier

Environment Details:
Version: 0.10.781.0

Repro steps:

  1. Turn on Narrator/NVDA
  2. Hit the URL ""aka.ms/terminal"" and install ""Windows terminal (Preview)"" application
  3. Open ""Windows terminal (Preview)"" application
  4. Tab to "Dropdown" control and press enter or use "Ctrl + Shift + Space"
  5. Tab till "About" and press enter
  6. Verify whether the "About" dialogue box is read immediately when the "About" dialogue box is opened

Actual Result:
Narrator/NVDA is not reading the name of the dialogue box immediately when the "about" dialogue box is opened

Expected Result:​
Narrator/NVDA should read the name of the dialogue box immediately when the "about" dialogue box is opened

User Impact:​
Screen Reader users will face difficulty if the name of the dialogue box is not read immediately when the "About" dialogue is opened because they don't understand what they opened

MAS Reference:​
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}

Bug_Narrator not reading dialogue box name immediately after opening the pop up.pptx

Bug_NVDA not reading dialogue box name immediately after pop up is opened.pptx

Originally created by @SpandanaPaladi on GitHub (Apr 20, 2020). #A11y_WindowsTerminal; #WindowsTerminal; #A11yMAS; #A11yTCS; #DesktopApp; #Win10; #C+E-H; #ScreenReader; #Narrator; #NVDA; #A11ySev2; #NonBenchMark; #MAS1.3.1 [Check out Accessibility Insights!](https://nam06.safelinks.protection.outlook.com/?url=https://accessibilityinsights.io/&data=02%7c01%7cv-shcha1%40microsoft.com%7cb67b2c4b646d4f9561a208d6f4b5c39b%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636965458847087032&sdata=uWx6cTEfazn%2BoCV3cL1iYB4KN%2BuXQ/MTlmOVec%2BZgKc%3D&reserved=0) - Identify accessibility bugs before check-in and make bug fixing faster and easier **Environment Details**: Version: 0.10.781.0 **Repro steps:** 1. Turn on Narrator/NVDA 2. Hit the URL ""aka.ms/terminal"" and install ""Windows terminal (Preview)"" application 3. Open ""Windows terminal (Preview)"" application 4. Tab to "Dropdown" control and press enter or use "Ctrl + Shift + Space" 5. Tab till "About" and press enter 6. Verify whether the "About" dialogue box is read immediately when the "About" dialogue box is opened **Actual Result:** Narrator/NVDA is not reading the name of the dialogue box immediately when the "about" dialogue box is opened **Expected Result:​** Narrator/NVDA should read the name of the dialogue box immediately when the "about" dialogue box is opened **User Impact:​** Screen Reader users will face difficulty if the name of the dialogue box is not read immediately when the "About" dialogue is opened because they don't understand what they opened **MAS Reference:​** https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4} [Bug_Narrator not reading dialogue box name immediately after opening the pop up.pptx](https://github.com/microsoft/terminal/files/4502445/Bug_Narrator.not.reading.dialogue.box.name.immediately.after.opening.the.pop.up.pptx) [Bug_NVDA not reading dialogue box name immediately after pop up is opened.pptx](https://github.com/microsoft/terminal/files/4502484/Bug_NVDA.not.reading.dialogue.box.name.immediately.after.pop.up.is.opened.pptx)
claunia commented 2026-01-31 01:05:23 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Apr 22, 2020):

Verified that this was fixed sometime between 0.10 and 0.11. Tagging appropriately.

@carlos-zamora commented on GitHub (Apr 22, 2020): Verified that this was fixed sometime between 0.10 and 0.11. Tagging appropriately.
claunia commented 2026-01-31 01:05:24 +00:00
Author
Owner
Copy Link

@Amulya-95 commented on GitHub (May 14, 2020):

Regressed the bug in latest environment. The issue is partially fixed, narrator is reading the 'About' dialog name when it is opened. But, NVDA is not reading the dialog name.
Please find the attachments for reference.

Attachments:
[Fixed]Bug 5419_Narrator is reading 'About' dialog name.pptx

[Not Fixed]Bug 5419_NVDA is not reading 'About' dialog name.pptx

@Amulya-95 commented on GitHub (May 14, 2020): Regressed the bug in latest environment. The issue is partially fixed, narrator is reading the 'About' dialog name when it is opened. But, NVDA is not reading the dialog name. Please find the attachments for reference. **Attachments:** [[Fixed]Bug 5419_Narrator is reading 'About' dialog name.pptx](https://github.com/microsoft/terminal/files/4627873/Fixed.Bug.5419_Narrator.is.reading.About.dialog.name.pptx) [[Not Fixed]Bug 5419_NVDA is not reading 'About' dialog name.pptx](https://github.com/microsoft/terminal/files/4627933/Not.Fixed.Bug.5419_NVDA.is.not.reading.About.dialog.name.pptx)
claunia commented 2026-01-31 01:05:24 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (May 19, 2020):

We're not doing anything special here. These are standard ContentDialog from WinUI. @DHowett-MSFT any suggestions on next steps here?

@carlos-zamora commented on GitHub (May 19, 2020): We're not doing anything special here. These are standard `ContentDialog` from WinUI. @DHowett-MSFT any suggestions on next steps here?
claunia commented 2026-01-31 01:05:24 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 19, 2020):

This may be related to #5623.

@DHowett commented on GitHub (May 19, 2020): This may be related to #5623.
claunia commented 2026-01-31 01:05:24 +00:00
Author
Owner
Copy Link

@cinnamon-msft commented on GitHub (Jun 2, 2020):

Should the Resolution-Fix-Available tag be removed?

@cinnamon-msft commented on GitHub (Jun 2, 2020): Should the Resolution-Fix-Available tag be removed?
claunia commented 2026-01-31 01:05:25 +00:00
Author
Owner
Copy Link

@Amulya-95 commented on GitHub (Jun 12, 2020):

@carlos-zamora, @cinnamon-msft Could you please confirm whether the issue is external to NVDA.

If it is external to NVDA, please provide Sample App so that we can log external bug to NVDA team and close this bud since it is working with Narrator.

@Amulya-95 commented on GitHub (Jun 12, 2020): @carlos-zamora, @cinnamon-msft Could you please confirm whether the issue is external to NVDA. If it is external to NVDA, please provide Sample App so that we can log external bug to NVDA team and close this bud since it is working with Narrator.
claunia commented 2026-01-31 01:05:25 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jun 16, 2020):

Performed some further investigation. Turns out that this is not an issue with NVDA, but rather an issue with XAML Islands. A ContentDialog with a hyperlink is not presented properly via screen readers.

This is an external bug being tracked by https://github.com/microsoft/microsoft-ui-xaml/issues/2681.

@Amulya-95 is this sufficient for us to close the bug, since there's nothing we can do but wait for a fix on their end?

@carlos-zamora commented on GitHub (Jun 16, 2020): Performed some further investigation. Turns out that this is _not_ an issue with NVDA, but rather an issue with XAML Islands. A ContentDialog with a hyperlink is not presented properly via screen readers. This is an external bug being tracked by https://github.com/microsoft/microsoft-ui-xaml/issues/2681. @Amulya-95 is this sufficient for us to close the bug, since there's nothing we can do but wait for a fix on their end?
claunia commented 2026-01-31 01:05:25 +00:00
Author
Owner
Copy Link

@Amulya-95 commented on GitHub (Jun 16, 2020):

@carlos-zamora Current bug can not be closed.
As per C&AI External bug process we will take action on the current bug, once the external bug is fixed and fixes are available in the testing environment.

@Amulya-95 commented on GitHub (Jun 16, 2020): @carlos-zamora Current bug can not be closed. As per [C&AI External bug process](https://microsoft.sharepoint.com/teams/ceacc/SitePages/External-Bug-process.aspx) we will take action on the current bug, once the external bug is fixed and fixes are available in the testing environment.
claunia commented 2026-01-31 01:05:25 +00:00
Author
Owner
Copy Link

@Amulya-95 commented on GitHub (Jun 17, 2020):

@cinnamon-msft SLA cannot be changed. However, if required you can follow Exclusion Process.

@Amulya-95 commented on GitHub (Jun 17, 2020): @cinnamon-msft SLA cannot be changed. However, if required you can follow [Exclusion Process](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmicrosoft.sharepoint.com%2Fteams%2Fceacc%2FSitePages%2FExternal-Bug-process.aspx&data=02%7C01%7Cv-amus%40microsoft.com%7Cdf5e765e185843978c7c08d81207b497%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637279171887052552&sdata=y4ihErJhFRhybxx4BdvBI%2BH%2B9sJmlSsmP7DrJB3MlfA%3D&reserved=0).
claunia commented 2026-01-31 01:05:25 +00:00
Author
Owner
Copy Link

@cinnamon-msft commented on GitHub (Jun 18, 2020):

Per the exclusion process:

Importance of Experience
Low impact. The title of the dialog box is not automatically read out loud upon opening.

Quality of Experience
Low impact. The user can still tab to the dialog box title in order for it to be read out loud by a screen reader.

AAT Conformance Doc listed under "Windows Terminal - Win32": https://cloudblogs.microsoft.com/industry-blog/government/2018/09/11/accessibility-conformance-reports/

@cinnamon-msft commented on GitHub (Jun 18, 2020): Per the exclusion process: **Importance of Experience** Low impact. The title of the dialog box is not automatically read out loud upon opening. **Quality of Experience** Low impact. The user can still tab to the dialog box title in order for it to be read out loud by a screen reader. AAT Conformance Doc listed under "Windows Terminal - Win32": https://cloudblogs.microsoft.com/industry-blog/government/2018/09/11/accessibility-conformance-reports/
claunia commented 2026-01-31 01:05:26 +00:00
Author
Owner
Copy Link

@Amulya-95 commented on GitHub (Jun 19, 2020):

@Alexandria-R as per the above comments could you please take appropriate action on this bug.
Thanks!

@Amulya-95 commented on GitHub (Jun 19, 2020): @Alexandria-R as per the above comments could you please take appropriate action on this bug. Thanks!
claunia commented 2026-01-31 01:05:26 +00:00
Author
Owner
Copy Link

@Alexandria-R commented on GitHub (Jun 19, 2020):

We need written acceptance of the bug from the external team before this can be processed for exclusion.

@Alexandria-R commented on GitHub (Jun 19, 2020): We need written acceptance of the bug from the external team before this can be processed for exclusion.
claunia commented 2026-01-31 01:05:26 +00:00
Author
Owner
Copy Link

@cinnamon-msft commented on GitHub (Aug 31, 2020):

@Alexandria-R Do the comments on this filed bug on their repository count as written acceptance, or is there a formal process we need to follow? https://github.com/microsoft/microsoft-ui-xaml/issues/2681

@cinnamon-msft commented on GitHub (Aug 31, 2020): @Alexandria-R Do the comments on this filed bug on their repository count as written acceptance, or is there a formal process we need to follow? https://github.com/microsoft/microsoft-ui-xaml/issues/2681
claunia commented 2026-01-31 01:05:26 +00:00
Author
Owner
Copy Link

@Alexandria-R commented on GitHub (Aug 31, 2020):

That should do! Please attend office hours to discuss the bug.

@Alexandria-R commented on GitHub (Aug 31, 2020): That should do! Please attend office hours to discuss the bug.
claunia commented 2026-01-31 01:05:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 28, 2023):

Possibly related to https://github.com/microsoft/microsoft-ui-xaml/issues/5909 or #11295.

Nevermind. This looks like it was fixed at some point in the past. Maybe MUX 2.8?

@zadjii-msft commented on GitHub (Sep 28, 2023): ~Possibly related to https://github.com/microsoft/microsoft-ui-xaml/issues/5909 or #11295.~ Nevermind. This looks like it was fixed at some point in the past. Maybe MUX 2.8?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Accessibility Issue-Bug Product-Terminal Resolution-External Tracking-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7495
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?