Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

accessibility: Ctrl+Home then Down arrow key go to system bar for WebView2 app #10241

Open
danny8002 opened this issue Dec 17, 2024 · 0 comments
Labels
accessibility Narrator, keyboarding, UIA, etc area-WebView bug Something isn't working product-winui2

Comments

@danny8002
Copy link

Describe the bug

Seems WinUI2 is not well-integrated with WebView2 for accessibility issue in scan mode. Ctrl+Home will move focus to the top of the webpage content, but subsequent down arrow presses will navigate to the app system bar.

try Win32 + WebView2, this issue don't repro. so this should be WinUI2 bug.

Steps to reproduce the bug

  1. Launch the sample app https://github.com/MicrosoftEdge/WebView2Samples/tree/main/GettingStartedGuides/WinUI2_GettingStarted/MyUWPGetStartApp

  2. (optional) Update WinUI2 2.8.6, WebView2 1.0.2903.40

  3. Turn On Narrator, "Tap" to one of page elements

  4. "Caps Lock" + "Space" to turn on scan mode

  5. Press Ctrl + Home to move to the top of the content.

  6. Use the down arrow key to start navigating the content.
    => hear "MyUWPGetStartApp" from system bar
    expect => the next element of the page content

Expected behavior

Actual:
After pressing Ctrl+Home, the screen reader first moves focus to the top of the webpage content, but subsequent down arrow presses navigate to system bar like the title bar, minimize button, maximalize button

Expected:
Focus should remain within the content after using Ctrl+Home, and down arrow navigation should continue consistently from the top of the webpage content without jumping through other elements like the system title bar.

Screenshots

No response

NuGet package version

WinUI 2 - Microsoft.UI.Xaml 2.8.2

Windows version

Windows 11 (24H2): Build 26100

Additional context

No response

@danny8002 danny8002 added the bug Something isn't working label Dec 17, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label Dec 17, 2024
@karkarl karkarl added accessibility Narrator, keyboarding, UIA, etc area-WebView product-winui2 and removed needs-triage Issue needs to be triaged by the area owners labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Narrator, keyboarding, UIA, etc area-WebView bug Something isn't working product-winui2
Projects
None yet
Development

No branches or pull requests

2 participants