Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds:A11y_Aspire Dashboard_Settting_Console log_AI4W

[kapilvaishna]

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

Leveraging SWE Agent can help accelerate this accessibility bug fix; review and validate all AI generated changes before merge.

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

#A11yAuto; #A11yTCS; A11yMAS; #A11ySev2; #DesktopWeb; #Win11; #Chrome; #Aspire; #E2E_AspireDashboard_Web_May2026; #WCAG1.4.3; #Devtools; #FTP; #copilot:agent=a11yagent; #ES Chat; #AI4W;

Issue Subcategory

Low contrast text

User Experience

Users with low vision or impaired contrast sensitivity cannot read the text. This is one of the most common accessibility barriers on the web.

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 > Console tab > Run fats pass > Observe issue: Users with low vision or impaired contrast sensitivity cannot read the text. This is one of the most common accessibility barriers on the web.

Issue:

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds (color-contrast - https://accessibilityinsights.io/info-examples/web/color-contrast)

Target application:

TestShop console logs - https://testshop.dev.localhost:16319/consolelogs

Element path:

.log-line-row-container:nth-child(2) > .log-line-row.console-line-row > .log-line-area[role="log"][b-su4p9d2w5e=""] > .log-content[b-su4p9d2w5e=""] > .resource-prefix[b-su4p9d2w5e=""]

How to fix:

Fix any of the following:
Element has insufficient color contrast of 3.88 (foreground color: #000000, background color: #8e6038, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1

Environment: Microsoft Edge version 150.0.0.0

====

This accessibility issue was found using Accessibility Insights for Web 2.47.0 (axe-core 4.11.3), a tool that helps find and fix accessibility issues. Get more information & download this tool at http://aka.ms/AccessibilityInsights.

Environment details

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

Attachment

[joperezr]

🤖 Aspire triage pass — 2026-05-26 09:05 UTC

Area: area-dashboard
Kind: bug (accessibility)
Repro: yes-minimal — see Repro Steps section of the issue body (TestShop dashboard ▸ Console logs ▸ resource prefix element)
Affected version(s): not specified; latest 13.3.x
Severity: S3 — WCAG 2 AA color-contrast failure on the resource-prefix label in the dashboard console-log view; visual readability degraded for low-vision users, but no functional break and a workaround exists (different theme / browser zoom).

Urgency: ⚪ backlog — no milestone
Reason: S3 a11y polish bug in the dashboard; no regression baseline cited, no servicing-blocker signal.

Suggested owner(s): @JamesNK
Evidence:

• @JamesNK merged a very high volume of area-dashboard PRs in the last 30–90 days (e.g. Update blazor.web.js to latest version in 11p4 #17445, Show empty state for console logs #17340 review, Add install CLI link to AI Agents dialog descriptions #17331, Fix stack overflow when opening child dialog from notification center #17261, Fix Manage button overlapping Close button in Settings dialog at high zoom #17258, 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) — by far the top contributor to this area.

Confidence: medium
Needs human?: yes — triage owner should decide whether to assign to the dashboard a11y workstream vs. accept as-is; bot cannot judge a11y priority.

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