[✨ Triage] dotnet/aspire#10129 by AnKushSingh05 - Unexpected backward focus navigation triggered by Shift + Tab: A11 ...

[MihuBot]

Triage for microsoft/aspire#10129.
Repo filter: area-dashboard issues.
MihuBot version: a1770b.
Ping MihaZupan for any issues.

This is a test triage report generated by AI, aimed at helping the triage team quickly identify past issues/PRs that may be related.
Take any conclusions with a large grain of salt.

dotnet/aspire#10129: Unexpected backward focus navigation triggered by Shift + Tab: A11y_Aspire Dashboard_FocusOrder by AnKushSingh05
[Tool] Searching for Shift + Tab focus navigation, focus order accessibility, keyboard navigation Aspire Dashboard, A11y focus order, unexpected focus movement, WCAG 2.4.3 (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Found 54 issues, 134 comments, 54 returned results (13534 ms)

Here are related issues and discussions relevant to issue #10129 ("Unexpected backward focus navigation triggered by Shift + Tab: A11y_Aspire Dashboard_FocusOrder"):

---

Highly Related Recent Issues

Issue #10127 (June 2025) - Keyboard focus is coming out of the "Copilot chat" dialog: A11y_Aspire Dashboard_Copilot_FocusOrder

• Summary: Reports that keyboard focus can escape the "Copilot chat" dialog, violating expected focus order and causing accessibility issues for keyboard and screen reader users.
• Relevance: Also concerns focus order and keyboard navigation in the Aspire Dashboard, specifically with dialogs. No comments yet, but the scenario and tags are nearly identical.

Issue #10119 (June 2025) - Keyboard focus does not return to the parent control after closing the Help, Github copilot and settings dialog: A11y_Aspire Dashboard_ResourcesFocusOrder

• Summary: After closing dialogs, focus does not return to the previously focused parent control, causing confusion for keyboard and screen reader users.
• Relevance: Focus order and restoration is a recurring accessibility concern in the dashboard, especially after modal interactions.

Issue #10118 (June 2025) - Sort and Resize buttons are not accessible using the keyboard keys: A11y_Aspire Dashboard_Resources_Keyboard.

• Summary: Sort and resize buttons are not accessible via keyboard, impacting keyboard and screen reader users.
• Relevance: Another recent accessibility issue in the "Resources" tab, indicating ongoing focus and keyboard navigation problems.

---

Older, Closed, or Broader Issues

Issue #3363 (April 2024, Closed) - When we navigate using TAB key after the table keyboard focus moves to top of the page instead of moving to next interactive control.:A11y_.NetAspireDashboard_Processruntimedotnetassembliescount_Table view_Keyboard.

• Summary: TAB navigation after a table incorrectly moves focus to the top of the page. This was fixed and verified as of April 2024.
• Relevance: Demonstrates a history of focus order bugs in the dashboard, with fixes applied.

Issue #3362 (April 2024, Closed) - When we close "Details view" section focus moves to top of the page: A11y_.NetAspireDashboard_Resource_Details view_Keyboard

• Summary: Focus moved to the top of the page after closing a details view, rather than returning to the triggering control. Fixed and verified.
• Relevance: Similar focus restoration issue, now resolved.

Issue #3173 (March 2024, Closed) - List options under 'Type filter' button are not accessible by keyboard: A11y_.NetAspireDashboard_Resource_Filter_Keyboard.

• Summary: Keyboard navigation in filter popovers was not working as expected. Multiple PRs and comments discuss workarounds and limitations in FluentUI/Blazor.
• Relevance: Focus and keyboard navigation in popovers/menus, with discussion of underlying component limitations and workarounds.

Issue #3315 (April 2024, Closed) - Extra TAB is required to activate the links present in the table.:A11y_A11y_.NetAspireDashboard_Resources_Grid_Keyboard

• Summary: Extra TAB was needed to activate links in tables. Marked as "by design" due to interaction model.
• Relevance: Shows the complexity of keyboard navigation in grid/table scenarios.

---

General Accessibility/Focus Order Tracking

Issue #270 (October 2023, Closed) - Dashboard Accessibility Issues

• Summary: General tracking of accessibility issues, including focus order, aria-labels, and real-time updates.
• Relevance: Demonstrates ongoing attention to accessibility, with some items split into separate issues.

Issue #346 (October 2023, Closed) - Accessibility Issues in FluentUI Blazor Components or FluentUI Web Components

• Summary: Tracks accessibility issues that are due to underlying component libraries.
• Relevance: Some focus order issues may be rooted in third-party component behavior.

---

Additional Notes

• There are several merged PRs addressing keyboard navigation and focus order, especially in popovers and dialogs (see #3568, #4243, #3368).
• Many of these issues are tagged with #A11ySev2, #WCAG2.4.3, #FocusOrder, and #Keyboard, indicating a pattern of related accessibility concerns in the dashboard UI.
• The most recent issues (June 2025) suggest that focus order and keyboard navigation remain active areas of concern, particularly in modal/dialog and tabbed navigation scenarios.

---

Summary

• Issue #10129 is part of a cluster of recent accessibility issues in the Aspire Dashboard, all related to keyboard focus order and navigation, especially in dialogs and tabbed interfaces.
• There is a history of similar bugs, some of which have been fixed, but new regressions or unaddressed scenarios continue to be reported.
• Underlying component behavior (FluentUI/Blazor) has contributed to some of these issues, and workarounds or fixes have been discussed and implemented in several PRs.
• No direct fix or workaround is documented for the specific "Shift + Tab" backward navigation bug in the "Resources" tab, but the pattern of issues and fixes suggests it is part of a broader, ongoing effort to improve keyboard accessibility.

---

If you are triaging this issue, it should be grouped with other recent focus order and keyboard navigation bugs, and may benefit from reviewing recent changes to dialog/tab focus management and any upstream component updates.