Triage for microsoft/aspire#10130.
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#10130: Visually appearing "Container: account" is not defined as heading: A11y_Aspire Dashboard_View details_Heading. by AnKushSingh05
[Tool] Searching for heading accessibility, semantic heading, screen reader heading, WCAG 1.3.1, Info and Relationships, dashboard heading, Container: account heading, A11y heading (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=False, Repository=dotnet/aspire)
[Tool] Found 129 issues, 59 comments, 129 returned results (20341 ms)
Here are the most relevant related issues and discussions for issue #10130 ("Visually appearing 'Container: account' is not defined as heading: A11y_Aspire Dashboard_View details_Heading."):
Highly Related Accessibility/Heading Issues
Issue #10125 (June 2025) - "The 'Help' dialog contains incorrect heading levels: A11y_Aspire Dashboard_Resources_Heading."
- Summary: Reports that the "Help" dialog in the Aspire Dashboard uses incorrect heading levels, making it difficult for screen reader users to understand the page structure. The expected result is for headings to use appropriate semantic levels (h1, h2, h3, etc.).
- Discussion: No comments, but the issue is extremely similar in nature: both are about missing or incorrect semantic heading markup in the dashboard, impacting screen reader navigation and WCAG 1.3.1 compliance.
- Status: Closed July 2025.
Issue #168 (September 2023) - "Ensure dashboard is accessible"
- Summary: General tracking issue to ensure the Aspire dashboard meets accessibility requirements, including use of
aria-* labels, real-time updates, and proper roles.
- Discussion: Comments note that most items are complete except for live regions, and emphasize using appropriate roles for elements.
- Status: Closed January 2024.
Issue #270 (October 2023) - "Dashboard Accessibility Issues"
- Summary: Tracks specific accessibility bugs, including missing labels and attributes, and mentions color contrast issues. One item is about ensuring select elements and buttons have proper labels.
- Status: Closed October 2023.
Issue #1392 (December 2023) - "clickable divs are inaccessible as written"
- Summary: Notes that clickable divs should be buttons or have proper roles/labels for accessibility.
- Status: Closed January 2024.
Issue #1123 (November 2023) - "Accessibility and screen reader support for metrics"
- Summary: Discusses the need for accessibility and screen reader support in the metrics pages, including announcing new data.
- Status: Closed February 2024.
Issue #2681 (March 2024) - "Accessibility onboarding for .NET Aspire Dashboard"
- Summary: Tracks onboarding and review of accessibility scenarios, including fixing bugs identified by accessibility tools and testers.
- Status: Closed March 2024.
Other A11y/Screen Reader Issues in the Dashboard
Issue #10123 (June 2025) - "Screen reader is announcing the incorrect number of rows number as 8, even though there are only 7 rows available"
- Summary: Screen reader announces the wrong number of rows in a table, causing confusion for users.
- Status: Open.
Issue #10142 (June 2025) - "Screen reader does not announce the status message indicating the number of results"
- Summary: Screen reader does not announce status messages, such as the number of results found.
- Status: Open.
Issue #10299 (July 2025) - "Screen reader is not announcing the checked/unchecked status for helpful/unhelpful buttons"
- Summary: Screen reader does not announce the state of certain buttons, impacting accessibility.
- Status: Open.
General Observations
- There is a pattern of accessibility issues being reported for the Aspire Dashboard, especially regarding headings, roles, and screen reader navigation.
- Issue #10125 is the most directly related, as it also concerns heading levels and semantic markup for screen readers.
- Several older issues (e.g., #168, #270, #1392) show that accessibility is an ongoing area of improvement, with some items closed as fixed and others tracked for future work.
- The dashboard has had multiple rounds of accessibility review and onboarding (#2681), but new issues continue to be reported as the UI evolves.
Summary Table
| Issue # |
Date Opened |
Title |
Status |
Key Points |
| #10125 |
June 2025 |
The "Help" dialog contains incorrect heading levels |
Closed |
Same root cause: missing/incorrect heading markup, WCAG 1.3.1 |
| #168 |
Sep 2023 |
Ensure dashboard is accessible |
Closed |
General a11y tracking, including headings/roles |
| #270 |
Oct 2023 |
Dashboard Accessibility Issues |
Closed |
Specific a11y bugs, including labels/roles |
| #1392 |
Dec 2023 |
clickable divs are inaccessible as written |
Closed |
Emphasizes semantic elements for a11y |
| #1123 |
Nov 2023 |
Accessibility and screen reader support for metrics |
Closed |
Screen reader support for dynamic content |
| #2681 |
Mar 2024 |
Accessibility onboarding for .NET Aspire Dashboard |
Closed |
Onboarding and review of a11y scenarios |
| #10123 |
Jun 2025 |
Screen reader announces wrong row count |
Open |
Table a11y issue |
| #10142 |
Jun 2025 |
Screen reader does not announce status message |
Open |
Status message a11y issue |
| #10299 |
Jul 2025 |
Screen reader not announcing button state |
Open |
Button state a11y issue |
Conclusion
- Issue #10130 is part of a broader set of accessibility issues in the Aspire Dashboard, especially regarding semantic headings and screen reader navigation.
- The most directly related prior issue is #10125, which requests correct heading levels for dialog content.
- There is a history of accessibility reviews and fixes, but new issues continue to be reported as the UI changes.
- The team should ensure that all visually prominent section labels (like "Container: account") are marked up with appropriate heading tags (e.g.,
<h2>) to comply with WCAG 1.3.1 and improve screen reader navigation.
Let me know if you need a deeper dive into any specific issue or want to see the full comment history for any of the above!
Triage for microsoft/aspire#10130.
Repo filter:
area-dashboardissues.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.
Here are the most relevant related issues and discussions for issue #10130 ("Visually appearing 'Container: account' is not defined as heading: A11y_Aspire Dashboard_View details_Heading."):
Highly Related Accessibility/Heading Issues
Issue #10125 (June 2025) - "The 'Help' dialog contains incorrect heading levels: A11y_Aspire Dashboard_Resources_Heading."
Issue #168 (September 2023) - "Ensure dashboard is accessible"
aria-*labels, real-time updates, and proper roles.Issue #270 (October 2023) - "Dashboard Accessibility Issues"
Issue #1392 (December 2023) - "clickable divs are inaccessible as written"
Issue #1123 (November 2023) - "Accessibility and screen reader support for metrics"
Issue #2681 (March 2024) - "Accessibility onboarding for .NET Aspire Dashboard"
Other A11y/Screen Reader Issues in the Dashboard
Issue #10123 (June 2025) - "Screen reader is announcing the incorrect number of rows number as 8, even though there are only 7 rows available"
Issue #10142 (June 2025) - "Screen reader does not announce the status message indicating the number of results"
Issue #10299 (July 2025) - "Screen reader is not announcing the checked/unchecked status for helpful/unhelpful buttons"
General Observations
Summary Table
Conclusion
<h2>) to comply with WCAG 1.3.1 and improve screen reader navigation.Let me know if you need a deeper dive into any specific issue or want to see the full comment history for any of the above!