Accessibility Android

[bruzzers]

• I have read the Getting Started section
• I have already searched for the same problem

Environment

Technology	Version
Flutter version	3.7.11
Plugin version	5.7.2+3
Android version	33
iOS version	x
macOS version	x
Xcode version	x

Device information: all Android

Description

Using this version of the plugin when the talkback recognise the web view, when swipe talkback not move to web page elements but to the next element of the app. If I move to 5.7.1+2 version of plugin it work correctly. I think the change in 5.7.2 broke something inside the accessibility and talkback.

[github-actions]

👋 @bruzzers

NOTE: This comment is auto-generated.

Are you sure you have already searched for the same problem?

Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem!

If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue.

In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding android WebView [MY ERROR HERE] or ios WKWebView [MY ERROR HERE] keywords.

Following these steps can save you, me, and other people a lot of time, thanks!

[Ray13]

Hi, I too have the same problem.

The problem is systematic and we have not found a solution online.
Accessibility not working, other flutter webview plugins read accessibility correctly.

[liranzairi]

Have the same problem too, had to revert back to v5.7.1+2

[ajanec01]

Hi @pichillilorenzo
The issue is cased by the removal of the options.useHybridComposition constraint in c2ce274. I've had some experience with screen readers and noticed that they can be a bit fussy when working with an overflow. It looks like it's something to do with the layout params for pull to refresh.

[moheb-badawy]

Semantics is completely broken for inAppWebView on Android and iOS.

Could you please provide an update on when this problem might be resolved, @pichillilorenzo ?

[Velliane]

Hi,
I have the problem too with version 6.0.0. Can this be resolved ?

[pichillilorenzo]

I'm not able to reproduce the issue. I'm using latest version of the plugin and Flutter 3.24.3.
This is a real Android device and Talkback is working correctly:

test.mp4

[ueman]

@pichillilorenzo Did you at any point tap directly into the webview? In that case it works for me, but I can't get into the webview by using exclusively the talk back gestures.

[pichillilorenzo]

Sorry, I only tapped to the WebView, didn’t handle it with talk back gestures.
So I need to test it again.

[pichillilorenzo]

It will be fixed with version 6.2.0-beta.2.
You can try the master branch, thanks.

[pichillilorenzo]

Released new version 6.2.0-beta.2 with the fix.

[bossPsw]

해당 버그를 수정하여 새로운 버전을 출시했습니다 6.2.0-beta.2.
@pichillilorenzo Even after updating, TalkBack still cannot recognize the content. The same issue persists even when turning TalkBack on and off within the app.

[pichillilorenzo]

@bossPsw post minimal code to reproduce the issue and a screen recording, thanks.

[pichillilorenzo]

I was able to reproduce the issue: TalkBack works correctly the first time is activated, but if you turn it off and on again while the Flutter app is still running, TalkBack will not recognize the WebView (Flutter PlatformView) anymore.

It seems to be related to how Flutter PlatformView currently works under the hood.
Indeed, here is the official Flutter issue about it: flutter/flutter#158004
It seems that the Flutter team should fix it.

[bossPsw]

Thank you for your answer. I always use flutter inappview well. I wish for your continued development 2024년 11월 29일 (금) 19:11, Lorenzo Pichilli ***@***.***>님이 작성:

…

I was able to reproduce the issue: TalkBack works correctly the first time is activated, but if you turn it off and on again while the Flutter app is still running, TalkBack will not recognize the WebView (Flutter PlatformView) anymore. It seems to be related to how Flutter PlatformView currently works under the hood. Indeed, here is the official Flutter issue about it: flutter/flutter#158004 <flutter/flutter#158004> It seems that the Flutter team should fix it. — Reply to this email directly, view it on GitHub <#1694 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABPQR4IOCTISGM22UZD7AIT2DA4VRAVCNFSM6AAAAAAZGKUDQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBXGQ4DQNRWGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue.