[✨ Triage] dotnet/aspire#10142 by AnKushSingh05 - Screen reader is announcing the incorrect number of menu items as ...

[MihuBot]

Triage for microsoft/aspire#10142.
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#10142: Screen reader does not announce the status message indicating the number of results:A11y_Aspire Dashboard_Resources_Screenreader. by AnKushSingh05
[Tool] Searching for screen reader status message, screen reader announce results, A11y status message, WCAG 4.1.3, NVDA status message, Narrator status message, Aspire Dashboard screen reader (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Found 42 issues, 78 comments, 42 returned results (17260 ms)

Here are the most relevant related issues and discussions for issue #10142 ("Screen reader does not announce the status message indicating the number of results:A11y_Aspire Dashboard_Resources_Screenreader"):

---

1. PR #1514 (Dec 2023) - Adds live region to console log status + rows

• Summary: This PR added ARIA live regions to the console log status text and new console log rows, based on MDN accessibility guidance. The intent was to ensure that screen readers announce changes in these areas.
• Relevance: Shows prior work to make status messages and dynamic content accessible to screen readers, but focused on console logs, not resource result counts.

---

2. PR #1513 (Dec 2023) - Add aria attributes to clickable divs, add aria-live attributes to console log status + log rows

• Summary: Similar to #1514, this PR added ARIA attributes to improve accessibility, including aria-live for status messages in the console log area. It also improved accessibility of clickable divs.
• Relevance: Reinforces that ARIA live regions have been considered for status messages, but again, the focus was on console logs.

---

3. Issue #1124 (Nov 2023, closed Dec 2023) - Accessibility and screen reader support for console logs

• Summary: This issue called for improved keyboard and screen reader support in console logs, specifically ensuring logs are read line-by-line. It was closed as being subsumed by #168, which included adding live regions.
• Relevance: Indicates a general push for live region support, but not specifically for result counts in the Resources tab.

---

4. Issue #168 (Sep 2023, closed Jan 2024) - Ensure dashboard is accessible

• Summary: A broad accessibility tracking issue. One checklist item was "Any real-time updates announcing changes, etc." A comment notes that live regions were the last major missing piece.
• Relevance: Confirms that live regions for dynamic updates were a known requirement, but does not specify implementation for result counts in Resources.

---

5. Issue #10123 (June 2025, open) - Screen reader is announcing the incorrect number of rows number as 8, even though there are only 7 rows available:A11y_Aspire Dashboard_Resources_Screenreader.

• Summary: Reports that the screen reader announces the wrong number of rows in the Resources tab. The user impact is confusion for visually impaired users.
• Relevance: Highly related, as it also concerns screen reader announcements of result counts in the Resources tab. However, it is about incorrect numbers being announced, not the absence of an announcement.

---

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

• Summary: Tracked onboarding and fixing of accessibility bugs, with a checklist for reviewing and fixing Sev1 and Sev2 bugs.
• Relevance: Indicates ongoing accessibility work, but does not discuss status message announcements specifically.

---

7. PR #7075 (Jan 2025, merged) - Fix displaying status message in span details

• Summary: This PR fixed an issue where status messages in span details were not displayed correctly. The discussion mentions status messages and their keys, but in the context of tracing and span details, not resource result counts.
• Relevance: Related to status messages, but not to the Resources tab or result count announcements.

---

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

• Summary: This large PR improved layout and accessibility for low-vision and mobile users, including toolbar and detail view accessibility. Comments mention that "Search count reflects the # of rows displayed on page based on search" and that context is preserved when filters are applied.
• Relevance: Indicates that the UI does display the number of results, and that this is updated with search/filter actions. However, there is no explicit mention of whether this count is announced to screen readers via ARIA live regions.

---

9. Issue #270 (Oct 2023, closed Oct 2023) - Dashboard Accessibility Issues

• Summary: Tracked various accessibility issues, including labels and color contrast, but not live region announcements for result counts.
• Relevance: General accessibility improvements, but not directly related to the current issue.

---

10. PR #1380 (Dec 2023, merged) - 5 small a11y fixes

• Summary: Fixed several accessibility issues, including missing labels and color contrast, but not live region announcements.
• Relevance: General accessibility improvements, not specific to result count announcements.

---

Summary and Conclusions

• There has been significant work on accessibility, including ARIA live regions for console log status messages and general dashboard updates.
• The most closely related open issue is #10123, which also concerns screen reader announcements of result counts in the Resources tab, but focuses on incorrect numbers being announced rather than the absence of an announcement.
• PR #4245 confirms that the UI does update the result count when filters/searches are applied, but there is no explicit evidence that this count is announced to screen readers.
• No issue or PR was found that directly addresses the absence of a screen reader announcement for the number of results in the Resources tab.
• The general accessibility tracking issues (#168, #2681, #270) and related PRs show ongoing improvements, but do not specifically resolve the problem described in #10142.

---

Recommendation

• #10142 appears to be a valid, new accessibility issue: while the UI updates the result count, there is no evidence that this is announced to screen readers via ARIA live regions or similar mechanisms.
• It is related to #10123, but distinct (that issue is about incorrect numbers, not missing announcements).
• Reference prior work on ARIA live regions in console logs (PRs #1513, #1514) as examples of how this could be addressed for the Resources tab.

---

Related Issues and PRs

• Issue #10123 (June 2025) - Screen reader is announcing the incorrect number of rows number as 8, even though there are only 7 rows available:A11y_Aspire Dashboard_Resources_Screenreader.
• PR #1514 (Dec 2023) - Adds live region to console log status + rows
• PR #1513 (Dec 2023) - Add aria attributes to clickable divs, add aria-live attributes to console log status + log rows
• PR #4245 (May 2024, merged July 2024) - Improve summary details view / toolbars / navbar experience on desktop for low-vision users, as well as mobile users
• Issue #168 (Sep 2023) - Ensure dashboard is accessible
• Issue #2681 (Mar 2024) - Accessibility onboarding for .NET Aspire Dashboard

---

If you need to reference prior work or suggest a fix, point to the ARIA live region implementations in the console log area as a model for how to announce result counts in the Resources tab.