Keyboard focus moves to "Installation Successfully Completed" text after close button but focus indicator is not visible.: A11y_ .NET SDK and CLI_InstallationScreen_Keyboard

[PoojaNamde]

Github Tags:

#A11yTCS; #A11yMAS; #WCAG2.4.3; #A11ySev3; #ScreeReader; #E2E_.NET SDK and CLI_Win32_Jul2026; #DesktopApp; #FTP; #.NET SDK and CLI; #FocusOrder; #a11ydb-static-in-tab-order;

Issue Subcategory:

A few static elements are in the tab order

User Experience:

Keyboard users encounter a few unnecessary tab stops on non-interactive content, which adds minor effort to reach the actual controls but does not break navigation

Repro Steps:

Open .net sdk preview> Installation screen>Install>Installation Successfully Completed > Observed the issue.

Actual Result:

After pressing TAB on the Close button, keyboard focus moves to the "Installation Successfully Completed" text. However, the text does not have a visible focus indicator, making it impossible for keyboard users to determine where focus has landed.

Expected Result:

Keyboard focus should move only to interactive elements, or if focus lands on an element, a visible focus indicator must be provided so users can identify the current focus location.

How to Fix:

Remove tabindex="0" from non-interactive elements so only interactive controls are in the tab order; if an element must be programmatically focusable for focus management, use tabindex="-1" so it stays out of the default tab sequence of the interface

Environment details:

Application Name: .NET SDK and CLI
OS: Windows 11 Enterprise Insider Preview 26300.8276

Note:

"Contact CAI Accessibility Support Channel 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:

55634_Keyboard.mp4

[github-actions]

🎯 Agentic Issue Triage

Triage Assessment:

• 🏷️ Labels: Area-dotnetup Work items around the proposed `dotnetup` bootstrapper/toolchain management tool and library Bug cookie Issue Monster Loves Cookies!
• 💻 Assignment: @marcpopMSFT | @dotnet/dotnetup

@dsplaisted had 2 recently created open untriaged issues assigned in the past week; @marcpopMSFT had 1, so @marcpopMSFT was selected.

• 🟩 Confidence: high - The issue clearly describes an accessibility bug in the dotnetup installation screen.

Similar issues: #55606 (potentially related)

➡️ Summary: Keyboard focus lands on the non-interactive "Installation Successfully Completed" text without a visible focus indicator in the dotnetup installer. Review focusable element handling in the installation completion screen to ensure proper focus indicator visibility.

Generated by 🏷️ Issue Triage for #55634 · 45.7 AIC · ⌖ 6.38 AIC · ⊞ 10.1K · ◷

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent (base branch: main).

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster Orchestrator · auto · 20.6 AIC · ⌖ 0.46 AIC · ⊞ 12.7K · ◷