Screen reader announces surrounding content along with "Learn more" link.: A11y_ .NET SDK and CLI_InstallationScreen_ScreenReader
- Dominant language
- C#
- Stars
- 3.2k
- Forks
- 1.3k
- PR merge metrics
- PR metrics pending
Description
### Github Tags:
#A11yTCS; #A11yMAS; #WCAG4.1.2; #A11ySev3; #ScreeReader; #E2E_.NET SDK and CLI_Win32_Jul2026; #DesktopApp; #FTP; #.NET SDK and CLI; #NameRoleValue; #a11ydb-link-name-extra-info;
### Issue Subcategory:
Link name has extra information
### User Experience:
Overly verbose names make it harder to tell which part of the announcement matters, degrading the listening experience as people either need to interrupt the screen reader repeatedly or sit through excessive announcements. For people who use voice control to activate a link by speaking its accessible name, a long name can make the link harder to target
### Repro Steps:
Open .net sdk preview> Installation screen> Learn more link> Observed the issue.
### Actual Result:
When keyboard focus moves to the "Learn more" link, the screen reader announces the entire descriptive content above the link instead of announcing only the link text. This results in excessive and repetitive information being conveyed to users.
### Expected Result:
When focus lands on the "Learn more" link, the screen reader should announce only the link text (or a concise, meaningful accessible name) without reading unrelated surrounding content.
### How to Fix:
Make the link's accessible name describe only the link destination or action. Remove unrelated text from naming sources while preserving any context needed to understand the link purpose
### Environment details:
Application Name: .NET SDK and CLI
OS: Windows 11 Enterprise Insider Preview 26300.8276
### Note:
"Contact [CAI Accessibility Support Channel](https://teams.microsoft.com/l/channel/19:DeCtYeREyQHw5jYsz9PPc3hpVw48m-tOlTkQ1jEn0eM1%40thread.tacv2/CAI%20Accessibility%20Support%20Channel?groupId=f5eb428c-9e6e-4c16-8143-33fe3961a9ae&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47) for Accessibility queries on design, development, test, usability or any processes"
Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
### Attachment:
https://github.com/user-attachments/assets/06877d0d-7185-4b7e-a66a-0200b7282d72
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue in the .NET SDK preview Installation screen on Windows 11, focusing on the “Learn more” link. Inspect how its accessible name is formed and verify with a screen reader that only a concise, meaningful link name is announced without unrelated surrounding content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- accessibility, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100