[Menu redesign 2025] Implement accessibility for all the menu items
Categories
(Firefox for Android :: Toolbar, task)
Tracking
()
People
(Reporter: skhan, Assigned: adhingra)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid][group3][menu-redesign-2025])
Attachments
(1 file, 1 obsolete file)
Verify and add all the accessibility items needed.
We will need to verify/add screen reader annotations, focus order, and whether interactive elements are properly labeled and navigable
https://www.figma.com/design/FWc4e0Z7ZZZOQwTxkhWo34/Menu-Handoff--WIP-?node-id=8335-9356&t=RNNmT6qsCDhBrjgj-4
Updated•2 months ago
|
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 1•2 months ago
|
||
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 10•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D254463
Updated•1 month ago
|
Comment 11•1 month ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: Users won't have the correct accessibility functionality for the menu.
- Code covered by automated testing: no
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Allow talkback and access menu and compare functionality with figma. More detailed steps available in the bugs marked as duplicate and see also on this bug.
- Risk associated with taking this patch: Low
- Explanation of risk level: Only changes accessibility features.
- String changes made/needed: Yes
- Is Android affected?: no
Comment 12•1 month ago
|
||
Flod, there are string changes in this uplift request, could your team chime in? Not sure who is in charge for Android string changes approvals. Thanks!
Comment 13•1 month ago
|
||
That would be Delphine (see also this page). Redirecting to her.
Is Android affected?: no
That's wrong, given the component?
Assignee | ||
Comment 14•1 month ago
|
||
From what I understand, this meant if the patch affects android device for example notifications or doing something related to battery. so in this case, it would be no. Please correct me if I am wrong!
Comment 15•1 month ago
|
||
I checked and these strings have already been translated in most languages, so they should already be in Beta. So in this case, it's safe to uplift.
Updated•1 month ago
|
Updated•1 month ago
|
Comment 16•1 month ago
|
||
uplift |
Comment 17•1 month ago
|
||
uplift |
Comment 18•1 month ago
|
||
This is backed out for causing Fenix build failures in CI:
https://treeherder.mozilla.org/jobs?repo=mozilla-beta&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=ab32f98a46735295222cf0f8998b7193d689b044&selectedTaskRun=J3kCbzVGQ6qmUbs1bvqUsg.0
Assignee | ||
Comment 19•1 month ago
|
||
Updated the patch, sorry about that, can we try again?
Comment 20•1 month ago
|
||
Comment on attachment 9499534 [details]
Bug 1970400 - Implement accessibility for all the menu items.
We are out of betas.
Comment 21•22 days ago
|
||
This issue is verified as fixed on Firefox for Android 142 (2025-07-20) on Samsung S24 Ultra (Android 15). Confirmed the results with :adhingra on Slack and filed a follow-up issue: Bug 1978365.
Updated•16 days ago
|
Comment 22•16 days ago
|
||
uplift |
Updated•16 days ago
|
Comment 23•16 days ago
|
||
uplift |
Comment 24•16 days ago
|
||
The updated patch is still causing build failures and I had to revert the uplift.
From the failure log:
https://treeherder.mozilla.org/logviewer?job_id=519757031&repo=mozilla-release
[task 2025-07-28T07:46:23.461+00:00] FAILURE: Build failed with an exception.
[task 2025-07-28T07:46:23.461+00:00]
[task 2025-07-28T07:46:23.461+00:00] * What went wrong:
[task 2025-07-28T07:46:23.461+00:00] Execution failed for task ':app:compileFenixDebugKotlin'.
[task 2025-07-28T07:46:23.461+00:00] > A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
[task 2025-07-28T07:46:23.461+00:00] > Compilation error. See log for more details
[task 2025-07-28T07:46:23.461+00:00]
[task 2025-07-28T07:46:23.461+00:00] * Try:
[task 2025-07-28T07:46:23.461+00:00] > Run with --stacktrace option to get the stack trace.
[task 2025-07-28T07:46:23.461+00:00] > Run with --info or --debug option to get more log output.
[task 2025-07-28T07:46:23.461+00:00] > Run with --scan to get full insights.
[task 2025-07-28T07:46:23.461+00:00] > Get more help at https://help.gradle.org.
[task 2025-07-28T07:46:23.461+00:00]
[task 2025-07-28T07:46:23.461+00:00] Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
[task 2025-07-28T07:46:23.461+00:00]
[task 2025-07-28T07:46:23.461+00:00] You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
[task 2025-07-28T07:46:23.461+00:00]
[task 2025-07-28T07:46:23.461+00:00] For more on this, please refer to https://docs.gradle.org/8.14.2/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
Unless we have a fix today before we build 141.0.1, the next target release for a working patch would be next week and 141.0.2.
Aaditya could you look at it please?
Assignee | ||
Comment 25•16 days ago
|
||
Hey, sorry we don't want to uplift this. Abandoned the patch! Sorry for the confusion!
Updated•16 days ago
|
Updated•15 days ago
|
Description
•