Screen reader does not capture the reduce protection infobar only the buttons
Categories
(Core :: Privacy: Anti-Tracking, defect)
Tracking
()
People
(Reporter: snegritas, Assigned: manuel)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Attachments
(4 files)
Found in
- 151.0a1(2026-04-09)
Affected versions
- 151.0a1(2026-04-09)
Tested platforms
- Affected platforms: Ubuntu 24.04, MacOS 26.3, Windows 10
Preconditions
- Set: privacy.reducePageProtection.infobar.enabled.pbmode to true
- Have screen reader on
Steps to reproduce
- Open a Private Brosing Window
- Navigate to https://www.pcgamer.com/games/rpg/borderlands-3-sometimes-felt-like-parody-of-itself-say-writers-but-4-aims-to-fix-that-if-i-tried-to-put-a-meme-in-the-game-he-would-come-to-my-house-with-a-baseball-bat/?__vfz=medium%253Dtray_notification#vf-e237d039-f241-47ef-bbcd-48108962ff73 and refresh once to trigger the Reduce page protection infobar.
- Navigate using TAB onto the infobar
Expected result
- Infobar should be captured and read what is it about.
Actual result
- Screen reader only captures the buttons inside the infobar without any context
| Assignee | ||
Comment 1•2 months ago
|
||
I've previously constructed the in a non-default way due to having
trouble with getting the formatting working. This doesn't seem to be a
problem, so reverting to the pattern how it is meant to be done.
Updated•2 months ago
|
Comment 3•2 months ago
|
||
| bugherder | ||
Comment 4•2 months ago
|
||
The patch landed in nightly and beta is affected.
:manuel, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox151towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 5•2 months ago
|
||
The feature is disabled in 151. No need to uplift.
| Reporter | ||
Updated•2 months ago
|
Updated•1 month ago
|
| Reporter | ||
Comment 6•1 month ago
|
||
Hello! Please see the attached screenshot with the issue. The button is captured inside the Reduce Protection infobar however there is still no description regarding the description of this button
| Reporter | ||
Updated•1 month ago
|
| Assignee | ||
Comment 7•1 month ago
|
||
Comment 9•18 days ago
|
||
| bugherder | ||
Comment 10•18 days ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 11•18 days ago
|
||
Adjusting bugzilla flags according to the info that this wasn't fixed with the first patch.
| Assignee | ||
Comment 13•7 days ago
|
||
I'm a bit torn about whether its good to uplift. We are somewhat late in beta (and it would be good to get this verified by qa) and the bug has been around for a long time (not the reducePageProtection bug itself, but the broader infobar bug).
However, 153 is the next esr, so having the fix uplifted to 153 would fix the accessibility bug also for the next esr users. The fix is also somewhat simple.
After weighting the above reasons I think I'm going to request uplift and also set QE flags for fix verification on the patch.
| Assignee | ||
Comment 14•7 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D304830
Updated•7 days ago
|
Comment 15•7 days ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: Some infobars (e.g. reduce page protection) and other using the same mechanism don't have their text read out by screen readers.
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: yes
- Steps to reproduce for manual QE testing: see comment 0
- Risk associated with taking this patch: low
- Explanation of risk level: Relatively simple fix. Patch verified by patch author and test. Setting QE to also verify the fix in beta.
- String changes made/needed?: no
- Is Android affected?: no
Updated•7 days ago
|
Updated•7 days ago
|
Comment 16•7 days ago
|
||
| uplift | ||
Updated•6 days ago
|
| Reporter | ||
Comment 17•6 days ago
|
||
Hello! I can confirm that the issue is fixed with firefox 154.0a1(2026-07-06) and 153.0b8 on Ubuntu 24.04 and MacOS 15.6.7.
I will update the status and flags of this issue have a nice day!
Description
•