Regression: WebView2 keyboard navigation with Tab key not getting registered (accessibility issue)

[lukajustic]

Description On WebView2 (version 114.0.1823.51) the tab key is not registered and a customer cannot navigate the app using tab key. This is bad for accessibility.

Version SDK: Microsoft.UI.Xaml 2.8.4 Runtime: 114.0.1823.51 Framework: Win32 OS: Win10

Regression Yes, last time I tested this in 114.0.1823.37 there was no issue

Repro Steps I used demo MyUWPGetStartApp from here: https://github.com/MicrosoftDocs/edge-developer/blob/main/microsoft-edge/webview2/get-started/winui2.md

1.) Open the demo app 2.) Click on "Tab" key. 3.) It should start putting elements in focus yet it doesn't

Interesting observation:

• Once I right click and open dev tools the tabbing starts working. However closing and opening the app will once again make tabbing not work
• Also minimising the app and then un-minimising also makes the tab start working

AB#45395518

[novac42]

Thanks for reporting the issue. I've assigned this to a dev that can help follow up on this.

[tofuandeve]

Hi I tried this on our UWP test app with Webview2 Runtime version 114.0.1823.58 and the issue doesn't seem to repro. Could you try it out on the later version of Webview Runtime to see if this issue still repro for you?

[lukajustic]

We've tested this issue on 114.0.1823.58 on multiple devices using both demo MyUWPGetStartApp and our custom app. The issue is still there.

Make sure you do not minimise the app after first launch as minimisation makes the issue go away. The problem is with first app load.

[tofuandeve]

@lukajustic I was using Microsoft.UI.Xaml 2.8.2, updated to 2.8.4, launch the UWP sample app and make sure to not trigger any of the mentioned flows (right clicking, minimizing/maximizing the app) and when I tab into the webview I can see the bounding box around the elements, for example a link, and can use keyboard to interact with the element (navigating to the link by pressing enter).

3.) It should start putting elements in focus yet it doesn't - Could you provide some more info on this? Were you able to see the bounding boxes at all when you tab into the webview?

[lukajustic]

Yes this is exactly the experience I would expect, and no, there were no bounding boxes. We tried on Microsoft.UI.Xaml 2.8.4 with 114.0.1823.58 runtime on Windows 10 device.

[tofuandeve]

@lukajustic Hey, I got the issue to repro on the UWP MyUWPGetStartApp sample app. This issue seems to be related to another issue that we have with WinUI2. This is issue is being investigated in the current sprint for us.

[tofuandeve]

hi @lukajustic We're talking to WinUI team to figure out the root cause of this issue right now. Could you do a quick check with webview2 runtime version 114.0.1823.37, I see that you mention the issue wasn't there for that version, but it seems to repro for me for that runtime version and the versions before that.

[maitreyee06]

hi @tofuandeve, me and my team are working on a project, and seem to be running into this same issue. Do you know when this issue will be fixed?

[VishyBala007]

Any update on this same issue I am also facing first time tabs dont work, then open anything else then come back it works.

Once lost focus fires then got focus fire then only it works.. By default you launch it wont work..

[champnic]

This is fixed in WinAppSDK/WinUI3 version 1.6+. The WinUI team isn't doing updates to UWP WebView2 anymore, so unfortunately I don't think we'll get a fix for this in UWP.