Question: When is a GeckoView *not* important for accessibility?

(In reply to Marco Zehe (:MarcoZ) from comment #2) > Question: When is a GeckoView *not* important for accessibility? My use case was for a DAISY book: I'm playing the audio files (text of the book) and using the GeckoView to display the content at the same time (e.g. text or image). I didn't find a way to prevent Talkback from reading the GeckoView while the audio is playing, so my workaround for now is to call View::setImportantForAccessibility to enable/disable the accessibility when the book is paused/played. There is probably a cleaner way to handle that, but that's how I found this "bug"... More precisely, the bug is the following: if one uses setImportantForAccessibility to make the GeckoView not important for accessibility (assuming there is a good reason to do that), the View is indeed no longer accessibility focusable but if you load a content into the GeckoView, Talkback still reads info like "page loading" etc