@akash07k - Thanks for the bug report! WebView2 uses UIA for its accessibility tree. If you try the Narrator screen reader it should work correctly. We have a known issue with JAWS and NVDA, though we are in contact with them about adding the support to correctly read the UIA tree. I'll link this to our work item adding that support.

If you also see your issue with Narrator then please let me know, as something else may be broken.

@champnic
Actually This issue has started reproducing since around 2 weeks.
Previously the webview2 was completely accessible with all the screen readers.
I've tried with Narrator, and although it reads the things in the scan mode, The tab navigation doesn't work properly and it doesn't read anything most of the time.
Alt+F4 also doesn't work for closing the application when we are inside webview.
This issues were not there 2 weeks before.
I don't think that it is UIA specific, NVDA supports UIA in edge webviews and I've tried explicitly turning on the UIA support in NVDA settings but same issue.
I think something is really broken up recently.

Do you have any idea what changed 2 weeks ago? OS update, runtime version change, or SDK change?

If you revert any of those (using previous SDK/runtime/OS) do you still see the issue?

@champnic
Actually I feel that runtime or sdk is updated since then, may be it is causing the issue.
I'm not sure though that which version was there previously.
I checked the issue on other builds of windows too, but it still persists everywhere.
Any way to downgrade the runtime?

Adding this bug to our backlog.

@akash07k All of our work goes onto our backlog, it is just a big list of all of our work. It does not imply priority.

This could be related to nvaccess/nvda#8553.
Note that, while Webview2 uses UIA, NVDA still uses the Chromium IAccessible2 implementation to expose the contents of the web view.

@LeonarddeR
In my opinion it's not related as this issue started to appear recently. And the issue on NVDA repo is almost 3-4 years old.

Thanks @akash07k.
I tried to test the app you provided, but it ends up in a break state shortly after starting. I'll have a test later this week to see whether I can reproduce this.

What's the current status of this issue?

Using NVDA, things seem to work properly, but using JAWS, they don't. Any ideas on that?

Any update on this issue? This provides a bad user experience.

I just tested this with the latest stable version of .NET 6.0, and this is what I found.

• Both NVDA and Narrator can detect when focus enters the WebView and interact with the content using UIA.
• JAWS cannot detect when focus goes inside the WebView and does not interact with the content. based on a conversation I had with Vispero this is something they are aware of and are working to resolve.

The issue that still remains, and it is a critical one in my opinion, is that key combinations such as Alt +F4 and Alt +Space bar do not work inside the WebView by default. this means that a keyboard user, screen reader user or not, will get trapped in the WebView unable to close the application or interact with the underlying window.

@rperez030 Would you mind specifically opening a new issue to track the "Alt+F4" and "Alt+Space" scenarios?

@champnic done - #2961 -. Please let me know if there is anything I should add.

@champnic Any update on this and on #2961 as well?
Both of these issues are not since fixed since 8 months now and sadly we are having very bad experience as such.
Not only Alt+F4, in fact if we once enter into the WebView, we can't go come outside of it by any pressing Shift+Tab or any other way.
Not only this, accessibility is still a big mess inside the WebViews with both JAWS, NVDA as well as Narrator.
Screen readers just read few controls via Tab key and after they stop recognizing any of the controls.
Only the Browse/Scan mode works which is not a good experience.
I really urge and request Microsoft that they seriously consider these both issues on priority and fix them.
Most of my apps based on WebView2 are completely unusable since all these months and I have some more full stack apps which I want to develop and I am unable to do so due to broken WebViews.
Please do not take these issues lightly. 🙏🙏🙏🙏🙏🙏

@champnic 1 update on this.
This seems that this issue is only happening with the WebView2 on WinUI based (MAUI too since it is based on WinUI).
I tried the same version of WebView2 with Tauri and none of the issues are present there.
Seems that there's something wrong with the implementation of WinUI.
I'll file the same issue on WinUI repo.

Adding to this, I am facing the same issue with JAWS and NVDA, both of them do not work and read out the elements. Alternatively, Narrator work well without any issue.

is any fix to this planned anytime soon?

This issue is currently being looked at; we will update here if there's a timeline.