The "NEW" badge text is not exposed to assistive technology
Categories
(Firefox for Android :: Contextual AI, defect)
Tracking
()
| Accessibility Severity | s2 |
People
(Reporter: ayeddi, Unassigned)
References
Details
(Keywords: access, good-first-bug, Whiteboard: [fxdroid][group1])
Attachments
(1 file)
Steps to reproduce
- Have TalkBack running
- Open Nighly on any webpage
- Navigate to and activate
More optionsbutton (kebab/app menu) - Navigate to and activate
Morebutton in the app menu - In the expanded menu, navigate to and focus with TalkBack the
Summarize pagebutton with aNEWbadge and observe the screen reader's announcement
Expected behavior
TalkBack announces the New text as part of the button' accessible name, i.e. Summarize page, New, before announcing the role of the control (button)
Actual behavior
TalkBack ignores the New text even though it is visually presented as a part of the button's visible label, it announces: Summarize page before announcing the role of the control (button). TB users won't be aware the badge is there at all.
Device information
- Firefox version: 152.0a1 (build #2016156887)
- Android device model: Samsung Galaxy A54
- Android OS version: 15
Any additional information?
Updated•6 months ago
|
Comment 1•6 months ago
|
||
The severity field is not set for this bug.
:matt-tighe, could you have a look please?
For more information, please visit BugBot documentation.
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Comment 2•5 months ago
|
||
The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:matt-tighe, could you consider increasing the severity?
For more information, please visit BugBot documentation.
Updated•4 months ago
|
Comment 3•1 month ago
|
||
| bug-fix | ||
Couldn't reproduce or verify this automatically (no Android build or emulator available), so it needs a developer to verify. The cause is clear from the code, though:
MenuItem() (fenix components/menu/compose/MenuItem.kt) uses clearAndSetSemantics, which sets contentDescription to the label plus description plus stateDescription. This drops the semantics of anything inside afterContent, including the StatusBadge. AddToTabGroupMenuItem works around this by passing the badge text as stateDescription. SummarizationMenuItem.kt does not.
Suggested fix in SummarizationMenuItem.kt (it isn't built yet):
val badgeText = stringResource(R.string.browser_menu_summarize_page_badge)
MenuItem(
label = stringResource(id = R.string.browser_menu_summarize_page),
stateDescription = if (summarizationMenuState.showNewFeatureBadge) badgeText else "",
...
afterContent = { if (summarizationMenuState.showNewFeatureBadge) StatusBadge(..., status = badgeText) },
)
The UI test selectors find this item by its exact content description, so they need to switch to substring matching:
summarizePageButton()inThreeDotMenuMainRobot.kt: addsubstring = true.SUMMARIZE_PAGE_BUTTONinMainMenuSelectors.kt: useCOMPOSE_BY_CONTENT_DESCRIPTION_SUBSTRING.
No other main-menu StatusBadge usage has this problem.
If you'd like to provide feedback on this comment, please use the 👍 or 👎 reaction.
Description
•