MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Narrator in Edge is not able to navigate virtualized tables
@champnic is already working on this.
Since Feb 2, 2022.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Description
When using the table shortcut keys in Narrator to navigate a table (ctrl+alt+arrow), if the table is virtualized, Narrator will not cause the table to load more rows, making the elements at the end of the current page unreachable.
Version
SDK:
Runtime: Version 97.0.1072.76 (Official build) (64-bit)
Framework:
OS: Win10 64 bit
Repro Steps
The bug can be reproduced in this codesandbox: https://codesandbox.io/s/blazing-voice-c48tq
Open Narrator and turn on scan mode (caps lock + space). Press 'T' to select the table. Navigate down the rows by repeatedly pressing ctrl+alt+down arrow.
Expected: Narrator moves down through all the rows as the user presses ctrl+alt+down
Actual: Narrator announces there is no next row after reaching the end of the first page of items and does not trigger the table to load the next set.
Screenshots
Additional context
This particular table's virtualization is implemented with an IntersectionObserver (https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API). It looks like Narrator is not causing an intersection event to fire even though it appears as if the page is scrolling. This issue does not exist with NVDA or JAWS, which is why I believe it is a bug in Narrator's implementation. Also, the issue can be observed in other virtualized tables so I don't believe it is an issue with the specific table implementation in the provided example. Here is another example I found that has the same issue https://codepen.io/abidibo/pen/ebPbKx
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.