Closed Bug 2063550 Opened 3 months ago Closed 1 month ago

[Windows] Trackers # is not announced on mouseover in the Privacy Widget

Categories

(Firefox :: New Tab Page, defect, P3)

Firefox 156
Desktop
Windows
defect

Tracking

()

VERIFIED FIXED
158 Branch
Accessibility Severity s3
Tracking Status
firefox156 --- wontfix
firefox157 --- wontfix
firefox158 --- verified
firefox159 --- verified

People

(Reporter: csasca, Assigned: rhamoui, NeedInfo)

References

(Blocks 1 open bug)

Details

(Keywords: access, Whiteboard: [hnt])

Attachments

(1 file, 1 external file)

Affected versions

  • Firefox Nightly 156.0a1 (2026-08-13)

Affected platforms

  • Windows 11

Preconditions

  • NVDA screenreader on
  • Have some blocked trackers shown inside the Privacy widget

Steps to reproduce

  1. Reach the Privacy widget in a new tab page
  2. Hover over the actual blocked trackers number

Expected result

  • The number is read by the screenreader

Actual result

  • The number is not read by the screenreader

Regression range

  • New feature

Additional Notes

The number is not read on hover which isn't ideal but not as severe as not read at all.

Accessibility Severity: --- → s3
Assignee: nobody → rhamoui
Whiteboard: [hnt]

Not ideal but not a launch blocker.

I'm not personally sure how to emulate this on a Macbook, and can't find the right resources.
Eitan, is there a way of emulating read-on-hover on MacOS Voiceover that can help me fix this bug?

Flags: needinfo?(eitan)

I'm not 100% sure this is reproducible on mac, you can try. Search for the accessibility preference "speak item under the pointer" and see if it works.

Flags: needinfo?(eitan)

Ah okay I was able to have the MacOS voiceover work with cursor navigation, and i was unable to reproduce the issue because the numbers were actually being read on my end. I've just attached a file for it.
Catalin, would you confirm if the issue is still persisting on your end?

Flags: needinfo?(csasca)

Well yes, macOS and Ubuntu works as expected, this one is specific for Windows and can confirm that this is still reproducible on Firefox 156.0a1 (2026-08-18) and Firefox 154.0 (with 156.1.20260818.43226 new tab addon) . For macOS we have only logged Bug 2063274.

Flags: needinfo?(csasca)
Severity: -- → S3
Priority: -- → P2

Hey Reem + all! I tested this on Windows with NVDA and Nightly 156.0a1 (2026-08-26). Here is a recording from the test. I was able to tab to the privacy widget and hear '88 trackers blocked today across 6 sites link' from NVDA. I encountered the same behavior Eitan mentioned where the number is not read on mouse hover (demonstrated in video).

Let me know if you need anything else!

Summary: [Windows][Screenreader] NVDA does not read the actual number of the blocked trackers inside the Privacy Widget → [Windows] Trackers # is not announced on mouseover in the Privacy Widget

Tested on Windows with Narrator and Nightly 157.0a1 (2026-08-31). I enabled 'Read and interact with the screen using the mouse' in Narrator settings and hovered over the trackers # by mouse. Narrator does not read the number, only reads 'trackers blocked today across 9 sites'. Given that I encountered the issue with NVDA and Narrator, I'm thinking this is a platform bug. I'll move this over to Core > Disability Access API

Severity: S3 → --
Component: New Tab Page → Disability Access APIs
Keywords: access
Priority: P2 → --
Product: Firefox → Core
Assignee: rhamoui → nobody
Severity: -- → S3
Priority: -- → P3

I don't see a privacy widget on the new tab page in Nightly, neither by default nor on the Manage Widgets page. browser.newtabpage.activity-stream.widgets.privacy.enabled is true in about:config. Is there some other pref I need to set?

Hi James!
here are the following prefs you'll need to enable to view the widget on New Tab:

  • browser.newtabpage.activity-stream.widgets.system.enabled
  • browser.newtabpage.activity-stream.widgets.system.privacy.enabled
Flags: needinfo?(jteh)

This is an interesting one. The reason this doesn't work with NVDA is that the visually rendered number - i.e. the node you would get when hit testing the screen coordinates - is hidden from the accessibility tree:

<span class="privacy-count-number" aria-hidden="true">1</span>

For mouse tracking, NVDA will always look for the deepest text node, but in this case, it gets nothing because the text node at those coordinates is aria-hidden.

Of course, the count is exposed to the accessibility tree, but that count is off-screen visually, so it can't be hit tested:

<span class="privacy-count-number-a11y">1</span>

I'm not really sure why there is a separate node (privacy-count-number-a11y) for accessibility purposes, rather than using the real count. That is generally not a good idea, precisely because it breaks hit testing. However, I guess there must have been a good reason for this. Reem, do you know why?

Flags: needinfo?(jteh) → needinfo?(rhamoui)

Hi Jamie, sorry this slipped from my radar! I'm catching up with it now.
I wasn't the one who implemented these 2 different span elements, however my conjecture from taking a deeper look, I think the second span tag (<span class="privacy-count-number-a11y">1</span>) was placed there because the first one (<span class="privacy-count-number" aria-hidden="true">1</span>) carried a number that would be updating in real-time/refresh if the number of trackers being blocked was increasing.

But, I don't really think it's necessary to have 2 separate tags to display the count. What we can do instead is keep the first one, remove the aria-hidden="true" attribute, and replace it with aria-live="polite" or aria-live="assertive" to indicate that if the number is updating.

That would probably clean up a bit of code, lessen future confusion, and screenreaders would be able to read what is neccessary.

What do you think?

Flags: needinfo?(rhamoui) → needinfo?(jteh)

(In reply to Reem Hamoui from comment #13)

I wasn't the one who implemented these 2 different span elements,

Right, and unfortunately, git blame isn't useful here. It seems this was landed as part of the initial code with no explanation as to why. I wonder if it's worth asking dgrant?

I think the second span tag (<span class="privacy-count-number-a11y">1</span>) was placed there because the first one (<span class="privacy-count-number" aria-hidden="true">1</span>) carried a number that would be updating in real-time/refresh if the number of trackers being blocked was increasing.

So the second "a11y" one doesn't get updated when the count increases? If I understand correctly, that means it might well contain stale information, which seems bad.

But, I don't really think it's necessary to have 2 separate tags to display the count. What we can do instead is keep the first one, remove the aria-hidden="true" attribute,

Sounds good to me, unless there's something else I'm missing.

and replace it with aria-live="polite" or aria-live="assertive" to indicate that if the number is updating.

I wouldn't add aria-live here. That would cause the number to be reported each time it updates, which will potentially result in excess verbosity that i don't think is useful to the user. Note that a screen reader user can still query for the information and they will receive the latest count. aria-live just determines whether the number gets reported automatically as soon as it changes.

That would probably clean up a bit of code, lessen future confusion, and screenreaders would be able to read what is neccessary.

I agree.

Flags: needinfo?(jteh)

Moving this back to HNT given that the fix here belongs in HNT code.

Severity: S3 → --
Component: Disability Access APIs → New Tab Page
Keywords: access
Product: Core → Firefox

The severity field is not set for this bug.
:thecount, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(sdowne)
Assignee: nobody → rhamoui
Status: NEW → ASSIGNED
Pushed by rhamoui@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/c09d4fdca024 https://hg.mozilla.org/integration/autoland/rev/151013c499b0 Fix tracker numbers not being announced on NVDA screen reader mouse over. r=Dre,Jamie
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 158 Branch

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

The patch landed in nightly and beta is affected.

:rhamoui, please make an uplift decision for beta:

  • Nominate the patch for beta uplift approval if the fix should be included in this release, or
  • Set status-firefox157 to wontfix if the fix can wait for the next release.

See Requesting an Uplift for documentation on how to request an uplift.

For more information, please visit BugBot documentation.

Flags: needinfo?(rhamoui)

This can train hop

Verified that the blocked trackers number is read as expected with NVDA on WIndows 11 with Firefox 159.0a1 (2026-09-25).

Status: RESOLVED → VERIFIED
QA Whiteboard: [S3][QA-5111][qa-found-in-c156] → [S3][QA-5111][qa-found-in-c156][qa-ver-done-c159/b158]

Verified that this is fixed as well on Firefox 158.0b2 on the same machine as in Comment 23.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: