MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: Narrator Left Arrow jumps to end of WebView2 content instead of previous elemen
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
When using Narrator in WebView2 content on Windows ARM64, pressing Left Arrow while focused on the first element causes Narrator to incorrectly jump to the last element in the document, instead of staying on the first element or doing nothing. This creates unexpected circular navigation behavior.
Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
143.0.3650.80 (arm64)
SDK Version
9.0.303
Framework
WinUI3/WinAppSDK
Operating System
Windows 11
OS Version
Version 10.0.26100 Build 26100
Repro steps
When a Narrator user navigates into WebView2 content:
- User presses Tab to enter WebView2 → Focus lands on first element
- User navigates forward with Right Arrow → Moves to next elements
- User navigates back with Left Arrow → Works correctly for middle/end elements
- BUG: When user is on the FIRST element and presses Left Arrow, Narrator jumps to the LAST element.
This creates unexpected "wrap-around" navigation that disorients screen reader users.
Expected Behavior
When user presses Left Arrow while on the first element in WebView2:
Option 1 (Preferred):
- Narrator should stay on the first element (no navigation)
- Similar to how reaching the end works in most documents
Option 2 (Acceptable):
- Narrator could play a boundary sound/announcement
- But should NOT jump to last element
Repros in Edge Browser
Yes, issue can be reproduced in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
No response
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.
Research direction
No repository files, tests, or entry points are mentioned. Start by reproducing the issue on Windows 11 ARM64 with WebView2 Runtime 143.0.3650.80 and compare the corresponding Edge version. The issue is done when Left Arrow at the first element no longer wraps to the last element.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100