[✨ Triage] dotnet/aspire#10139 by AnKushSingh05 - After applying resize, Copilot button is not visible: A11y_Aspire ...

[MihuBot]

Triage for microsoft/aspire#10139.
Repo filter: area-dashboard issues.
MihuBot version: 4431de.
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#10139: After applying resize, menu items are not accessible using keyboard: A11y_Aspire Dashboard_Keyboard. by AnKushSingh05
[Tool] Searching for keyboard accessibility menu resize, menu items not accessible after resize, A11y keyboard menu, WCAG keyboard menu, Aspire Dashboard keyboard accessibility, menu items inaccessible after zoom, keyboard navigation menu Aspire Dashboard (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Found 96 issues, 172 comments, 96 returned results (17169 ms)

Here are related issues and discussions relevant to issue #10139 ("After applying resize, menu items are not accessible using keyboard: A11y_Aspire Dashboard_Keyboard"):

---

Highly Related Recent Issues

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

• Summary: Reports that after running an Aspire project, the Sort and Resize buttons (and actions button) are not accessible via keyboard. The issue is tagged with WCAG2.1.1 and keyboard accessibility. The only comment is a request to file the issue in the correct repo.
• Relevance: Very similar scenario—keyboard inaccessibility of menu/buttons after resize or in certain states.

Issue #10141 (June 2025) - "After applying resize, .net aspire, help, copilot chat and settings buttons are not accessible: A11y_Aspire Dashboard_Resize."

• Summary: After resizing (zooming to 200%), several key buttons (help, copilot chat, settings) become inaccessible. The expected result is that these remain accessible and a scrollbar appears if needed.
• Relevance: Nearly identical environment and repro steps, but focused on different menu items. Suggests a broader pattern of keyboard accessibility issues after resizing/zooming.

---

Past Accessibility Issues and Fixes

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

• Summary: Keyboard navigation for dropdowns/menus was broken. The issue was traced to the FluentPopover component and its interaction with toolbars. Fixes involved updating to newer versions of fluentui-blazor and moving popovers outside toolbars. The issue was retested and confirmed fixed in v8.1.0-dev.
• Discussion: Extensive, including workarounds, retesting, and confirmation that the fix was in a package update. Also discusses the awkwardness of keyboard navigation and the need for further upstream fixes in FluentUI.
• Relevance: Shows that keyboard accessibility for menus has been a recurring issue, often related to component/library behavior and layout changes.

PR #4243 (May 2024) - "A11Y - Fix options under 'Type filter' button are not accessible by keyboard"

• Summary: Moved FluentPopover outside FluentToolbar to fix keyboard navigation. Details the technical reason: FluentToolbar was setting tabindex=-1 on sub-elements, breaking navigation.
• Relevance: Directly addresses a class of keyboard accessibility issues caused by layout/component structure.

PR #4245 (May–July 2024) - "Improve summary details view / toolbars / navbar experience on desktop for low-vision users, as well as mobile users"

• Summary: Major overhaul to improve accessibility and usability for low-vision and mobile users, including making toolbars and navigation menus more accessible and responsive to resizing/zooming. Includes many comments about scrollbars, menu accessibility, and keyboard navigation.
• Discussion: Multiple testers validated improvements to keyboard and low-vision accessibility, but also noted ongoing issues with state loss, scrollbars, and discoverability.
• Relevance: This PR and its discussion show ongoing work to address accessibility after resizing/zooming, with specific attention to keyboard access.

---

Other Related Issues

Issue #3257 (March–April 2024, closed) - "List options present under 'Level' combo box are not clearly visible after resizing to 200%"

• Summary: At 200% zoom, dropdown options were not visible. The issue was fixed and closed after retesting.
• Relevance: Shows that zoom/resize issues affecting accessibility have been previously addressed.

Issue #3175 (March–April 2024, closed) - "'Copy to clipboard' button under 'Source' column on the table is not accessible by keyboard keys"

• Summary: Keyboard inaccessibility of a button, fixed and closed after retesting.
• Relevance: Demonstrates a pattern of keyboard accessibility issues being reported and fixed.

Issue #3364 (April 2024–Sept 2024, open) - "There is no functionality provided to adjust columns width which is achievable using single pointer."

• Summary: Discusses both keyboard and pointer accessibility for resizing columns, with references to FluentUI examples and ongoing work to meet new accessibility requirements.
• Relevance: Shows that resizing and accessibility are a recurring theme, with ongoing work and evolving requirements.

---

General Accessibility Tracking

Issue #2681 (March 2024, closed) - "Accessibility onboarding for .NET Aspire Dashboard"

• Summary: Tracking issue for accessibility bugs, including review and validation of Sev1 and Sev2 bugs.
• Relevance: Indicates that accessibility is an ongoing area of focus, with multiple issues being tracked and addressed.

---

Summary

• Recent issues (#10118, #10141) report nearly identical problems with keyboard inaccessibility of menu/buttons after resizing or zooming, suggesting a broader, possibly unresolved pattern.
• Past issues and PRs (notably #3173, #4243, #4245) show that similar accessibility bugs have been fixed by updating component usage and layout, but new regressions or edge cases continue to appear, especially after UI changes or library updates.
• There is a history of accessibility issues being fixed and retested, but the recurrence of similar bugs (especially after resizing/zooming) suggests the need for ongoing vigilance and possibly more robust automated testing for these scenarios.

If triaging #10139, it should be linked to #10118 and #10141 as likely related, and referenced against the fixes and discussions in #3173, #4243, and #4245. It may also be worth checking if recent changes in the main branch or upcoming releases address this scenario, as similar issues have been fixed in the past but new regressions are possible.

---

Related Issues and PRs:

• #10118 (June 2025) - Sort and Resize buttons not accessible via keyboard
• #10141 (June 2025) - Help, Copilot, Settings buttons not accessible after resize
• #3173 (March 2024, closed May 2024) - List options under 'Type filter' button not accessible by keyboard
• PR #4243 (May 2024) - Fix options under 'Type filter' button not accessible by keyboard
• PR #4245 (May–July 2024) - Improve summary details view / toolbars / navbar experience for low-vision users
• #3257 (March–April 2024, closed) - Combo box options not visible after resizing to 200%
• #3175 (March–April 2024, closed) - 'Copy to clipboard' button not accessible by keyboard
• #3364 (April 2024–Sept 2024, open) - No functionality to adjust columns width with single pointer
• #2681 (March 2024, closed) - Accessibility onboarding for .NET Aspire Dashboard

Let me know if you need a more detailed summary of any specific issue or PR!