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

[MihuBot]

Triage for microsoft/aspire#10123.
Repo filter: area-dashboard issues.
MihuBot version: a1770b.
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#10123: 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. by AnKushSingh05
[Tool] Searching for screen reader incorrect row count, table row count accessibility, screen reader announces wrong number of rows, A11y table row count, Resources tab screen reader, WCAG1.3.1 table row count (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Found 52 issues, 139 comments, 52 returned results (12280 ms)

Here are the most relevant related issues and discussions for issue #10123 ("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."):

---

1. PR #1755 (Jan–Feb 2024) - Add data grid view of metrics

• Summary: This PR introduced an accessible table view for metrics, with a focus on screen reader support. It describes challenges with the Fluent Data Grid component, such as lack of live region/role support, and details a workaround where new row content is appended to an offscreen element with role=log for screen readers to announce.
• Relevant Discussion:
  • Concerns about how data disappearing from the grid (as it scrolls off) could confuse screen reader users, since rows may appear/disappear dynamically.
  • Comments on the importance of aggregate values for accessibility, as they reduce repetitive information for screen readers.
  • Issues with table count consistency (e.g., histogram table count not matching the chart).
• Takeaway: There is ongoing work and discussion about how dynamic row changes and virtualization in data grids can impact screen reader announcements, including row counts.

---

2. Issue #1081 (Nov 2023–Feb 2024) - Standardize grid selection and selected row display

• Summary: This issue discusses how selection and focus work in grids, including the Resources grid. It covers keyboard navigation, row selection, and how to indicate selection to screen readers.
• Relevant Discussion:
  • Comments highlight the need for keyboard-friendly selection and for screen readers to be able to identify which row is selected or actionable.
  • Discussion about using ARIA roles and making rows/cells focusable and executable for screen readers.
• Takeaway: Accessibility of grid navigation and selection is a known area of improvement, with specific attention to how screen readers interpret grid structure and row focus.

---

3. Issue #1123 (Nov 2023–Jan 2024) - Accessibility and screen reader support for metrics

• Summary: This issue is about ensuring accessibility and screen reader support for metrics pages, including announcing new data as it appears.
• Relevant Discussion: The need for additional testing and improvements for screen reader support in metrics tables.
• Takeaway: The team is aware of and working on screen reader support for dynamic data tables.

---

4. Issue #3174 (Mar 2024–Sep 2024) - Tooltips not available via keyboard in Resources page

• Summary: While not directly about row counts, this issue is about accessibility in the Resources tab, specifically tooltips not being accessible via keyboard, which is another aspect of screen reader support.
• Relevant Discussion: Discussion about using FluentTooltip and ensuring tooltips are read by screen readers.
• Takeaway: Accessibility improvements in the Resources grid are ongoing, with attention to screen reader compatibility.

---

5. Issue #3315 (Apr–Dec 2024) - Extra TAB required to activate links in table

• Summary: This issue is about keyboard navigation in tables, but the discussion includes how interactive controls in tables are accessed, which can affect screen reader users' experience.
• Relevant Discussion: The current design requires entering a cell to invoke actions, which may impact how screen readers announce row/column context.
• Takeaway: Table navigation and interaction design are being refined for accessibility.

---

6. PR #1231 (Dec 2023) - Highlight selected rows

• Summary: This PR adds visual highlighting for selected rows in grids, which is important for both sighted and screen reader users to understand context.
• Relevant Discussion: Comments about how selection is indicated and how it interacts with other row states.
• Takeaway: Visual and programmatic indication of selection is being improved, which can help screen readers announce the correct context.

---

7. PR #5200 (Aug 2024) - Make all pages accessible to low vision on reflow

• Summary: This PR addresses accessibility for low-vision users, including table presentation at different viewport sizes. There is extensive discussion about how tables behave, which columns are shown, and how content is announced or truncated.
• Relevant Discussion: Comments about how grid columns are managed, how content is trimmed or scrolled, and how these changes affect accessibility.
• Takeaway: The team is actively working on making tables more accessible, including for screen reader users, though the focus is more on layout than row count announcements.

---

8. Issue #10118 (June 2025) - Sort and Resize buttons not accessible by keyboard

• Summary: This is another accessibility issue filed by the same author as #10123, indicating ongoing accessibility testing and reporting in the Resources grid.
• Relevant Discussion: The issue is about keyboard access, but it shows that accessibility in the Resources grid is under active review.

---

Conclusions and Recommendations

• No direct duplicate of the specific "row count announced incorrectly" issue was found, but there is significant related discussion about accessibility of tables, screen reader support, and dynamic row changes in the Resources and Metrics grids.
• The most relevant technical context is in PR #1755 and Issue #1081, which discuss how dynamic data and virtualization can confuse screen readers about row counts and content.
• The team is aware of and working on accessibility issues in the Resources grid, including keyboard navigation, selection, and screen reader support.
• It may be helpful to reference the workaround in PR #1755 (using an offscreen element with role=log for screen readers) and the ongoing work to standardize grid accessibility.

---

Summary Table:

Issue/PR #	Date Opened	Title/Topic	Key Relevance
#1755 (PR)	Jan 2024	Data grid view of metrics, screen reader support	Dynamic rows, screen reader row count
#1081	Nov 2023	Standardize grid selection	Grid navigation, screen reader focus
#1123	Nov 2023	Accessibility for metrics	Screen reader support for tables
#3174	Mar 2024	Tooltips not accessible	Resources tab, screen reader
#3315	Apr 2024	Extra TAB for links	Table navigation, accessibility
#1231 (PR)	Dec 2023	Highlight selected rows	Visual/ARIA selection context
#5200 (PR)	Aug 2024	Reflow accessibility	Table layout, accessibility
#10118	Jun 2025	Sort/Resize not keyboard accessible	Ongoing accessibility review

If you need a more detailed summary of any specific issue or PR, let me know!