1907247 - [a11y] Touch exploration with TalkBack stops working in certain circumstances

Status: UNCONFIRMED

(Core :: Disability Access APIs, defect)

Description

[Diego Ramírez [:BlindMoon38]]

Steps to reproduce

1. Open Firefox with TalkBack enabled.
2. Select Duck Duck Go as the search engine and search for something, for example, Mozilla.
3. Explore the page with Touch exploration. Do not scroll the view. Notice that everything works normally.
4. Scroll to the bottom of the page and try touch exploration again. Notice that TalkBack doesn't focus any element in the web view.
5. Use TalkBack navigation gestures to explore the page. Notice that elements which aren't focusable with Touch exploration can be reached when using navigation gestures.
6. Browse to any URL, for example, Wikipedia.
7. Explore the page with Touch exploration. Notice how it works as expected.
8. Zoom the page and try touch exploration again. Notice that TalkBack can't focus elements while zoomed in.
9. Use navigation gestures to explore the page while still zoomed in. Notice how navigating with gestures is possible.

Expected behavior

In both 4 and 8 touch exploration doesn't work.

Actual behavior

Touch exploration should work always.

Device information

• Firefox version:Firefox Nightly 130.0a1 from2024-07-09T14:03:06.015268702.
• Android device model: Xiaomi Poco X6.
• Android OS version: HyperOS 1.0.6.0, Android 14.

Any additional information?

• TalkBack version 14.2.

Comment 1

[Diego Ramírez [:BlindMoon38]]

I just realised that I wrote Actual behaviour and Expected behaviour in each other's places, sorry.

Comment 2

[Diego Ramírez [:BlindMoon38]]

Just got the latest stable release, Firefox 128.0 is also affected.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:royang, could you have a look please?

For more information, please visit BugBot documentation.

Comment 4

[Roger Yang [:royang]]

Description:
Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s).
Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change.

How do we test this?
If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc.

When will this ship?
Tracking bug/issue:
Design documents (e.g. Product Requirements Document, UI spec):
Engineering lead:
Product manager:

The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible:
https://wiki.mozilla.org/Accessibility/Guidelines
Please describe the accessibility guidelines you considered and what steps you've taken to address them:

Describe any areas of concern to which you want the accessibility team to give special attention:

Comment 5

[James Teh [:Jamie]]

Thanks for the report.

Eitan, are you aware of any hit testing issues specific to Android, particularly with regard to scrolling, zoom and/or APZ? Any ideas?

Comment 6

[Eitan Isaacson [:eeejay]]

I can reproduce with Firefox. Interestingly the GeckoView sample browser works fine. This leads me to believe this is caused by how the browser view is embedded, or something in the vicinity. Will dig deeper.

Comment 7

[Eitan Isaacson [:eeejay]]

Unfortunately the regression happened when we switched to CtW explore by touch. This doesn't explain why the GeckoView sample app works fine.. will keep digging.

Comment 8

[James Teh [:Jamie]]

Assigning to :eeejay for now (with apologies) so the bot doesn't nag me as the one who introduced the regression. 😳

Comment 9

[Eitan Isaacson [:eeejay]]

(In reply to Diego Ramírez [:BlindMoon38] from comment #0)

6. Browse to any URL, for example, Wikipedia.
7. Explore the page with Touch exploration. Notice how it works as expected.
8. Zoom the page and try touch exploration again. Notice that TalkBack can't focus elements while zoomed in.
9. Use navigation gestures to explore the page while still zoomed in. Notice how navigating with gestures is possible.

I'm going to spin this into a new bug because it is a separate issue.

Comment 10

[Eitan Isaacson [:eeejay]]

OK bug 1927237 tracks the explore by touch behavior after pinch zooming.

Comment 11

[Eitan Isaacson [:eeejay]]

Attachment: Bug 1907247 - Update non-doc body element bounds when they change. r?morgan

Comment 12

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/718887ce7d31
Update non-doc body element bounds when they change. r=morgan