-
Notifications
You must be signed in to change notification settings - Fork 55
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
A11Y: WebView2 control is completely inaccessible with screen readers (NVDA, JAWS and parcially with Narrator too) #2330
Comments
@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 |
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 |
Adding this bug to our backlog. |
Please don't add it to backlog as it is a very severe issue and blocking
us from use the apps
|
@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. |
@LeonarddeR |
Thanks @akash07k. |
If you want to reproduce it early, then I can share the compiled build too.
Don't know why is it breaking at your end.
On 4/14/2022 2:14 PM, Leonard de Ruijter wrote:
Thanks @akash07k <https://github.com/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.
—
Reply to this email directly, view it on GitHub
<#2330 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBMZ7BIAU3JF4AGOQY3TVE7LILANCNFSM5SNLEGBA>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Signature “Innovation is the outcome of a habit, not a random act.”
“The power of the Tech is in its universality. Access by everyone
regardless of disability is an essential aspect.”
---
With Regards,
Akash Kakkar (He/His/Him)
Software Developer & Accessibility subject matter expert
|
Ping me on WhatsApp <https://wa.me/919716286389>
|
Follow me on Twitter <https://bit.ly/37cioC4>
|
Connect with me on Facebook <https://bit.ly/3u74ZEh>
|
Follow me on Linkedin <https://bit.ly/37fqJop>
|
Follow me on Github <https://bit.ly/3r29zBW>
|
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? |
It's still the same for me even with NVDA.
On Webview2 version 105.x
Still not fixed sadly
…On 9/9/2022 2:00 AM, Jordy Deweer wrote:
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?
—
Reply to this email directly, view it on GitHub
<#2330 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBM62JFXBWKNMOISLA3TV5JEGJANCNFSM5SNLEGBA>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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.
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. |
Yes, exactly, even here, with NVDA too I feel many issues with even the
latest webviews
…On 11/4/2022 9:37 PM, Roberto Perez wrote:
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.
—
Reply to this email directly, view it on GitHub
<#2330 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQWBM7UWMICVDZNKBRIZBTWGUYCNANCNFSM5SNLEGBA>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@rperez030 Would you mind specifically opening a new issue to track the "Alt+F4" and "Alt+Space" scenarios? |
@champnic Any update on this and on #2961 as well? |
@champnic 1 update on this. |
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. |
Hey Victor, It's been quite some time since the last update here. This looks like a pretty critical blocker for anyone adopting WebView2 in their app if they wish to remain accessible to all users. Can you provide any new information? How long can we expect this to remain unresolved, and what are some acceptable workarounds in the meantime? Thanks much! |
Looks like this was addressed in WinAppSDK 1.6 and serviced back to 1.5. If you are still running into an accessibility issue for a specific scenario, please open a new issue and we'll take a look. Thanks! |
I'm still seeing all same issues despite using 1.6 |
But, why do you want me to open the new issue if this issue itself is not fixed?
|
Because this bug that this issue was tracking has been fixed. As well as the other bug tracking Windows shortcuts. Unless you are saying you have no screen reader access at all in WinAppSDK? If that's not the issue you are running into, opening a new issue with the specific details of what you are trying to do, what's not working, version information for your setup, and sample code (if applicable) will be more beneficial than continuing this thread or increasing it's scope. |
hmm |
Description
The WebView is completely inaccessible with all of the screen readers.
Version
SDK: Windows App SDK 0.8.7 Stable as well as 1.1.0 Preview 1
Runtime: Microsoft Edge version 100.0.1185.29 as well as Microsoft Edge Canary version 102.0.1212.0
Framework: WinUI
OS: Win10(22581.200)
Repro Steps
The webview should be accessible with screen readers and we should be able to read and navigate the content flawlessly.
Screenshots
Attaching videos and the demo app code.
Additional context
Scarlett.zip
WebView2.Issue_1.mp4
WebView2.Issue_2.mp4
AB#38855066
The text was updated successfully, but these errors were encountered: