1862668 - [a11y] Fenix doesn't enter developer mode with Talkback enabled

Status: NEW

(Firefox for Android :: Settings, defect, P3)

Description

[Adina Petridean QA [:apetridean]]

Steps to reproduce

1. Turn TalkBack (or the available screen reader) on.
2. Launch Fenix and go to Settings -> About Firefox section.
3. Tap 12 times on the Firefox logo to enter into developer mode.
4. Observe the behaviour.

Expected behavior

When tapping on the 'Firefox Nightly' logo, the image is selected, and the application enters developer mode.

Actual result:

When tapping on the 'Firefox Nightly' logo, the image is not selected, and the application doesn't enter developer mode.

Device information

• Firefox version: 121.0a1 from 02.11.2023
• Android device model and OD version: Assus Zenfone 9 ( Android 13)

Any additional information?

Nothing happens when tapping on the logo from homepage or on the logo from About Section with Talkback enabled.
Please note that on Chrome, with Talkback enabled, the application enters developer mode.

Comment 1

[Adina Petridean QA [:apetridean]]

Anna Yeddi can you please take a look on this issue? We were uncertain about it.

Comment 2

[Anna Yeddi [:ayeddi]]

The image cannot be focused with TalkBack (it's marked as decorative so it is skipped while navigating with left/right swipes and it cannot be targeted with explore-by-touch). I am not aware of any alternative way to activate the developer mode.

Do you know about any workaround, @Eitan?

If there are none:

1. It is probably access-s2
2. possible fix: we could make the image focusable (add condentDescription of Firefox Nightly logo, for instance) and this should allow a TB user to focus it with TB and send multiple double-taps to activate the dev mode

Comment 3

[Eitan Isaacson [:eeejay]]

Don't know of an alternative. Your solution looks right. Note, I don't know if successive double taps would be fast enough but would need to experiment.

Comment 4

[Anna Yeddi [:ayeddi]]

(In reply to Eitan Isaacson [:eeejay] from comment #3)

Don't know of an alternative. Your solution looks right. Note, I don't know if successive double taps would be fast enough but would need to experiment.

I think that even one double-tap like on a regular button would be a better approach to not being able to activate it too

Comment 5

[Anna Yeddi [:ayeddi]]

As discussed above, since there are no alternative ways to activate the Debug mode with a screen reader, this is an access-S2 and I would encourage the triage owners to increase the severity of this bug for faster prioritization: while we do not expect all of our users to utilize this feature, this does create a full blocker for those who do need it while using an assistive technology.

Comment 6

[Jonathan Almeida [:jonalmeida]]

Thanks for the discussion and the ping!

This should be a higher severity which I've set to S3. My instinct was to set to S2, however, since this is a feature is meant for debugging which only a niche set of audience would need it falls into the S3 category, I think.

Would be happy to raise it higher as well if folks feel stronger about it.

Comment 7

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

The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:jonalmeida, could you consider increasing the severity?

For more information, please visit BugBot documentation.

Comment 8

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

The Bugbug bot thinks this bug should belong to the 'Fenix::Browser Engine' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.