Closed Bug 2030652 Opened 3 months ago Closed 18 days ago

Screen reader does not capture the reduce protection infobar only the buttons

Categories

(Core :: Privacy: Anti-Tracking, defect)

defect

Tracking

()

VERIFIED FIXED
154 Branch
Tracking Status
firefox151 --- wontfix
firefox152 --- wontfix
firefox153 --- verified
firefox154 --- verified

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

  1. Open a Private Brosing Window
  2. 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.
  3. 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

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.

Assignee: nobody → manuel
Status: NEW → ASSIGNED
Pushed by mbucher@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/b06b601601dc https://hg.mozilla.org/integration/autoland/rev/1e4f8ba3f07d Reduce Page Protection: Make strings in infobar captureable by screenreader r=timhuang
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 152 Branch

The patch landed in nightly and beta is affected.
:manuel, is this bug important enough to require an uplift?

For more information, please visit BugBot documentation.

Flags: needinfo?(manuel)

The feature is disabled in 151. No need to uplift.

Flags: needinfo?(manuel)
QA Whiteboard: [S3] [qa-found-in-c151] [QA-4834]
QA Whiteboard: [S3] [qa-found-in-c151] [QA-4834] → [S3] [qa-found-in-c151] [QA-4834][qa-triage-done-c153/b152][qa-ver-needed-c153/b152]
Flags: qe-verify+
Attached image IMG_1281.jpg

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

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Pushed by mbucher@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/5760d3d1ede0 https://hg.mozilla.org/integration/autoland/rev/e4bc9640097b Await l10n translation before setting alert role on infobar notifications r=tgiles
Status: REOPENED → RESOLVED
Closed: 2 months ago18 days ago
Resolution: --- → FIXED

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

Adjusting bugzilla flags according to the info that this wasn't fixed with the first patch.

Target Milestone: 152 Branch → 154 Branch
Keywords: access

Does this need a Beta uplift request?

Flags: needinfo?(manuel)
See Also: → 1895857

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.

Flags: needinfo?(manuel)
Attachment #9604686 - Flags: approval-mozilla-beta?

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
Attachment #9604686 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
QA Whiteboard: [S3] [qa-found-in-c151] [QA-4834][qa-triage-done-c153/b152][qa-ver-needed-c153/b152] → [S3] [qa-found-in-c151] [QA-4834][qa-triage-done-c153/b152][qa-ver-needed-c154/b153][uplift]
QA Contact: snegritas

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!

Status: RESOLVED → VERIFIED
QA Whiteboard: [S3] [qa-found-in-c151] [QA-4834][qa-triage-done-c153/b152][qa-ver-needed-c154/b153][uplift] → [S3] [qa-found-in-c151] [QA-4834][qa-triage-done-c153/b152][qa-ver-done-c154/b153][uplift]
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: