Pressing Enter on controls triggers multiple actions (control activation + row detail expansion):A11y_Aspire Dashboard_Resources_Keyboard

[kapilvaishna]

Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification.

Try ES Chat to learn more about the MAS rule and how to fix the issue. If you need more help, use our Teams channel or office hours.

"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; #WCAG2.1.1; #Keyboard; #FTP; #ES Chat; #Closed; #A11yFixed;

Issue Subcategory

Unexpected keyboard behavior

User Experience

Keyboard users are confused when controls behave differently from pointer interaction. Actions may produce different results or fail entirely when using the keyboard

Repro Steps

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 > More actions or Expand/Collapse child resources or Open in text visualizer >Observe issue: Pressing Enter on controls triggers multiple actions (control activation + row detail expansion)

Actual Result

Pressing ENTER performs two actions simultaneously:

• Activates the focused control
• Expands/activates the entire row (opens row details)

Expected Result

Pressing ENTER should trigger only the action of the focused control.
It should not also expand or activate the entire row.

How to Fix

Ensure keyboard and pointer interactions produce equivalent results. Bind the same action handler to both click and keyboard events. For complex widgets, document any non-standard keyboard interactions.

Environment details

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

Attachment

17651_Keyboard.mp4

[joperezr]

🤖 Aspire triage pass — 2026-05-29 07:11 UTC

Area: area-dashboard
Kind: bug (accessibility)
Repro: yes-minimal — see Repro Steps section of issue body
Affected version(s): not specified (latest: 13.4)
Severity: S3 — accessibility defect; non-blocking pointer-equivalent workaround exists

Urgency: 🟡 vNext — recommend milestone 13.5
Reason: A11y defect in dashboard table interaction; not a 13.4 regression of any newly-introduced feature, and a11y issues are typically batched rather than held against an already-snapped release.

Suggested owner(s): James Newton-King (@JamesNK) (score 126), backup Adam Ratzman (@adamint) (score 19)
Evidence:

• JamesNK merged 32 PRs labeled area-dashboard in the last 90d
• JamesNK closed 15 area-dashboard issues as completed in the last 180d
• CODEOWNERS lists James Newton-King (@JamesNK) and Adam Ratzman (@adamint) for /src/Aspire.Dashboard

Confidence: medium
Needs human?: no

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

[adamint]

Captured annotated before/after evidence for this issue:

• Evidence folder: https://github.com/adamint/aspire/tree/a11y-artifacts-20260601042635/17651
• Before video: https://github.com/adamint/aspire/blob/a11y-artifacts-20260601042635/17651/before/17651-before-fix.webm
• Before screenshot after Enter: https://github.com/adamint/aspire/blob/a11y-artifacts-20260601042635/17651/before/17651-before-fix-after-enter.png
• After video: https://github.com/adamint/aspire/blob/a11y-artifacts-20260601042635/17651/after/17651-after-fix.webm
• After screenshot after Enter: https://github.com/adamint/aspire/blob/a11y-artifacts-20260601042635/17651/after/17651-after-fix-after-enter.png

The before recording shows Enter on the focused Open in text visualizer row control opening both the text visualizer dialog and the row details pane. The after recording shows the same Enter key path opening only the text visualizer dialog while row details remain closed.

Draft fix PR: #17789

[kapilvaishna]

Issue is not repro so closing the bug.

Recording.7-01.at.13.40.1.webm