Issue metadata
Sign in to add a comment
|
Accessibility focus does not apply to elements in WebView.
Reported by
harumiyu...@gmail.com,
Dec 15 2017
|
||||||||||||||||||||||||
Issue description
Steps to reproduce the problem:
1. Start Lightning Web Browser and change UserAgent.
MENU->Settings->General Settings->User Agent->Custom
"Mozilla/5.0 (Linux; Android 6.0.1; F-04J Build/V16R071B; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/55.0.2883.91 Mobile Safari/537.36"
2. Enable TalkBack。
3. Display dMenu contents.
http://smt.docomo.ne.jp
4.Tap a link (Confirm reading aloud)
What is the expected behavior?
Accessibility focus on elements in WebView.
What went wrong?
Accessibility focus does not apply to WebView elements in dMenu content.
For other content, accessibility focus is applied to elements of WebView.
Did this work before? Yes 62.0.3202.66
Chrome version: 63.0.3239.83 Channel: stable
OS Version: Android 8.0.0
Flash Version:
I confirmed it with other mobile phones, but the Accessibility Event from Chromium was not notified.
,
Dec 18 2017
Tested the issue in Android and could not reproduce the issue. Observed the focus on the elements Steps Followed: 1. Enabled WebView #63.0.3239.111 2. Installed Lightning Web Browser and changed UserAgent to above mentioned 3. Enabled talkback 4. Navigated to http://smt.docomo.ne.jp 5. Observed the focus on the elements Chrome versions tested: 63.0.3239.111 OS Android 8.0.0, Android Devices 8.0.0; Pixel XL Build/OPR1.170623.027 @harumiyu2317: Could you please upgrade you WebView to the #63.0.3239.111 and check if you still face the issue? If so help us with the details of your device for further triaging? Thanks!!
,
Dec 19 2017
"sandeepkumars@chromium.org", Thank you for your comment. Updated to 63.0.3239.111 and confirmed. The occurrence frequency fell, but it was not completely corrected. The frequency of occurrence fell from 90% to 40%. If the problem does not occur, you can re-confirm the problem by reloading the page. Thanks
,
Dec 19 2017
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 10 2018
,
Jan 22 2018
,
Feb 26 2018
Play store link: https://play.google.com/store/apps/details?id=acr.browser.barebones&pli=1 I confirmed that this does use a webview. Paul, could confirm the bug? Is this a known accessibility change?
,
Feb 26 2018
Typo, I meant to say "could *you* confirm"
,
Feb 28 2018
I get no repro with shamu, Android N2G48J, TalkBack 5.0.4, WebView 55.0.2883.91 or 63.0.3239.83, after several attempts. Questions for harumiyu2317: - What TalkBack version do you repro with? - It might be helpful if you attach an adb bug report taken after repro'ing the bug. - When you say "the Accessibility Event from Chromium was not notified", does that mean you've debugged this yourself and looked for ax events in the code, or do you just mean you don't see accessibility working in the GUI? If the former, can you describe your investigation?
,
Mar 7 2018
>- What TalkBack version do you repro with? -> I was using 6.1.0.186797687. >- It might be helpful if you attach an adb bug report taken after repro'ing the >bug. -> As a result of checking at 65.0.3325.109, no event occurred. I reconfirmed it at 63.0.3239.111 where the problem occurred, but it also stopped occurring here. Because the content has changed, logs can not be acquired. >- When you say "the Accessibility Event from Chromium was not notified", does that mean you've debugged this yourself and looked for ax events in the code, or do you just mean you don't see accessibility working in the GUI? If the former, can you describe your investigation? -> It is the result of debugging by yourself. We added a log to requestSendAccessibilityEvent and confirmed it.
,
Mar 7 2018
After updating to that TalkBack version, I still get no repro, after several attempts. Do you know, what's the last good WebView version before this bug appeared? > Because the content has changed, logs can not be acquired. Do you mean the docomo website has changed, and now you can't repro either? If so, then there's probably nothing we can do.
,
Mar 7 2018
,
Mar 15 2018
>Do you know, what's the last good WebView version before this bug appeared? confirmed that there was no problem with the version number of 62.0.3202.66. > Do you mean the docomo website has changed, and now you can't repro either? If so, then there's probably nothing we can do. Yes. It seems that the content of docomo has been changed. Comparison is impossible because there is no past content.
,
Mar 15 2018
Please let us know if you find another way to repro. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pnangunoori@chromium.org
, Dec 18 2017