Manage button overlaps with Close button when screen is resized:A11y_Aspire Dashboard_Settings_Resize

[kapilvaishna]

Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification.
"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."

GitHub Tags

#A11yTCS; A11yMAS; #A11ySev2; #DesktopWeb; #Win11; #Chrome; #Aspire; #E2E_AspireDashboard_Web_May2026; #WCAG1.4.4; #Resize; #Keyboard;

Issue Subcategory

Overlapping content at zoom

User Experience

Enlarged text obscures other elements, making the UI unusable. Users cannot read overlapping content or interact with hidden controls.

Repro Steps

Change system resolution to 1280*768 and zoom browser size to 200% > Install Aspire CLI > Clone the Aspire repository https://github.com/microsoft/aspire/tree/main/playground/TestShop > From the console output, copy or open the Dashboard URL > Hamburger > Open setting > Observe issue: Manage button overlaps with Close button.

Actual Result

At 200% zoom, Manage button visually overlaps with the Close button, causing both controls to appear merged or partially hidden.

Expected Result

Layout should accommodate enlarged text without overlapping elements or obscuring content.

How to Fix

Use flexible layouts (CSS flexbox or grid) that reflow content. Avoid fixed-height containers for text content. Test at 200% zoom as part of QA.

Environment details

Application Name: Aspire Dashboard
Edition Windows 11 Enterprise
Version 25H2
OS build 26200.8390

Attachment

17254_Resize.mp4

[joperezr]

🤖 Aspire triage pass — 2026-05-19 11:22 UTC

Area: area-dashboard
Kind: bug (accessibility)
Repro: yes-minimal — see "Repro Steps" 1–6 in the issue body
Affected version(s): not specified by reporter; tested against Aspire Dashboard from main per repro
Severity: S3 — accessibility issue (WCAG 1.4.4 resize text) at 200% zoom on 1280×768 in the Dashboard Settings dialog; workaround is to use a larger viewport / lower zoom

Urgency: ⚪ backlog — no milestone
Reason: S3 accessibility polish in the Settings dialog; not a regression vs. 13.2 and no servicing signal. Could be picked up for 13.4 if dashboard A11y intake is being batched — flagging for owner judgment.

Suggested owner(s): @JamesNK (score ≈ 30), backup @adamint (score ≈ 2)
Evidence:

• @JamesNK authored the vast majority of recent area-dashboard merged PRs in the last 90 days (e.g. Always log dashboard startup summary across auth modes #17206, Keep canceled resource commands in dashboard notification center #17204, Calculate VerticalThreshold dynamically based on menu/popover content #17196, Improve version log messages in CLI, AppHost and dashboard #17163, Fix flaky test: Subscription_MultipleUpdates_MinExecuteIntervalApplied #16975, Fix traces != (not equals) filter returning empty results #16932, Enable static web assets in all environments for dashboard #16931, Add AI Agents dialog to dashboard header #16869, [release/13.3] Fix notification action closure over scoped services #16763, [release/13.3] Fix dashboard error in .NET 11 preview 4 #16761 — and many more)
• @adamint authored recent area-dashboard PRs Fix language dropdown arrow-key behavior and duplicate zh-CN entry in dashboard settings #16094 and Fix call stack exceeded frontend error by ensuring dialog close before nested dialog opens #14654

Confidence: high
Needs human?: no

Dry-run mode — no labels or milestone applied. Reply /triage apply to promote, or edit and reapply.

[JamesNK]

Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification.
"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."

How do you know to look at the bug when it is fixed?

[JamesNK]

Fixed