[Android M, UI Automator] Browser Accessibility getting turned on when uiautomator is used

[webkit...@gmail.com]

Hello,

I have been debugging one chrome performance issue on android M and I observed that accessibility is getting enabled for chrome as soon as I start some operations like automatic scroll using Android's UI Automator. Because of this we see high crRendererMain CPU utilization on M.

Accessibility is not getting enabled when I use UI Automator on Android L.

Is this a chromium bug or something to do only with Android's UI autoamator? I am asking this because I see some special handling in browser accessibility manager is done for android lollipop in chromium source.

Regards

Arun

[Dominic Mazzoni]

I'm not aware of a difference between Android L and M, that part is surprising.

On Android, UI Automator uses Android's accessibility APIs to query running apps. From the perspective of Chrome or Android WebView, it can't tell the difference between UI Automator running, and an accessibility service like TalkBack running. Unfortunately, enabling accessibility for the web is expensive, it needs to expose the entire DOM of the webpage via Android's accessibility APIs.

--
You received this message because you are subscribed to the Google Groups "Chromium Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-accessib...@chromium.org.

[Arun]

Thanks Dominic, I had some confusion because of LollipopBrowserAccessibilityManager.java, but it seems it is not the reason for accessibility not getting enabled on L when uiautomator is used.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-accessibility+unsub...@chromium.org.