Closed Bug 2063274 Opened 3 months ago Closed 2 months ago

[macOS][Voiceover] Privacy widget is seen as article, and nearly all the content inside is seen as clickable

Categories

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

Firefox 155
Desktop
macOS
defect

Tracking

()

VERIFIED FIXED
156 Branch
Accessibility Severity s3
Tracking Status
firefox155 --- wontfix
firefox156 --- verified

People

(Reporter: csasca, Assigned: rhamoui)

References

(Blocks 1 open bug)

Details

(Keywords: access, Whiteboard: [hnt])

Attachments

(1 external file)

Affected versions

  • Firefox Nightly 155.0a1 (2026-08-12)

Affected platforms

  • macOS 27

Preconditions

  • Voiceover on

Steps to reproduce

  1. Reach the Privacy widget in a new tab page
  2. Browse over it via the VO controls

Expected result

  • Voiceover will detect the content as expected

Actual result

  • The widget is seen as an "article" and nearly every focusable item inside is seen as "clickable"

Regression range

  • New feature

Additional Notes

Triage / fix plan (code reading only — not built or verified with VoiceOver).

The widget is React, not a custom element: browser/extensions/newtab/content-src/components/Widgets/Privacy/Privacy.jsx. Both symptoms come from its markup, and there are three distinct causes:

  1. "article" with no name. The root is a bare <article> with only className/ref — no heading and no aria-label/aria-labelledby (Privacy.jsx#505-519). .privacy-title-wrapper contains only the context-menu button, so VO announces an unnamed article. Peers name theirs with visible title text (Stocks newtab-stocks-widget-title, Crossword <h3>, Weather <h3>{city}</h3>); Privacy has none, and no newtab-privacy-widget-title string exists in newtab.ftl.

  2. "nearly everything is clickable." Not fake buttons — the opposite: one anchor wraps the entire content block. <a className="privacy-count"> (Privacy.jsx#588) encloses the icon, the count spans and both .privacy-count-text labels, and <a className="privacy-empty-details"> (Privacy.jsx#574-583) encloses the empty-state <p>. Every text node is therefore link content, and the link's computed name is the whole concatenated block.

  3. Unnamed menu button. The context-menu moz-button has no data-l10n-id/aria-label (Privacy.jsx#522-527), unlike Clocks/Stocks/PictureOfTheDay (newtab-*-widget-menu-button).

Proposed approach, in Privacy.jsx (+ a small _Privacy.scss tweak and new Fluent strings):

  • Give the article an accessible name: add a widget title element (visually-hidden if the design has no visible title) and point aria-labelledby at it, or data-l10n-id an aria-label.
  • Stop wrapping content in the anchors. Follow the pattern already used by Weather (Weather.jsx#422-431): an empty positioned overlay <a> carrying its own aria-label ("View protections"), with the count/label text as siblings outside it. Alternatively replace it with an explicit labelled CTA. Same for the empty state.
  • Add a newtab-privacy-widget-menu-button string and set it on the menu button.
  • The existing .privacy-count-number aria-hidden + visually-hidden .privacy-count-number-a11y pairing (Privacy.jsx#602-607) is already correct — keep it, but re-check for double-announcement once the anchor no longer wraps it.

Note the unnamed-<article> part is systemic across the Nova widget row (Lists, FocusTimer, Crossword, SportsWidget all do the same), so it may be worth a shared fix at the widget-wrapper level rather than only in Privacy.

Tests: no browser-chrome mochitest covers newtab widgets. The Jest test test/jest/content-src/components/Widgets/Privacy.test.jsx asserts structure by class only (one aria-hidden count test); role/accessible-name assertions should be added there.

Suggested severity: S3 — assistive-tech announcement quality is degraded, but the content stays reachable and actionable, and the widget is behind widgets.system.privacy.enabled (default false). Flagging for a11y review since I'm reasoning from the markup, not from a VoiceOver session.


If you'd like to provide feedback on this comment, please use the 👍 or 👎 reaction.
If you want to categorize your feedback you can add one of the following tags: ai-triage-wrong-file, ai-triage-wrong-cause, ai-triage-hallucination, ai-triage-out-of-scope.

Severity: -- → S3
Accessibility Severity: --- → s3

For other Widgets, what is the expected content type for the VO?

Flags: needinfo?(csasca)
Assignee: nobody → rhamoui
Whiteboard: [hnt]

Hey Helen, I think (but correct me if I'm wrong), the Voiceover should at least read "Privacy, article" instead of just "article", as it does on the Timer widget where it will read "Timer, article". Or better, if there is a possibility to make Voiceover see them as "Widget, privacy/timer/clocks", etc)?

Flags: needinfo?(csasca)

The VO is reading but just not being specific about it, so not a launch blocker.

Priority: -- → P2
Pushed by rhamoui@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/48b8fa122b55 https://hg.mozilla.org/integration/autoland/rev/ebbbc04e6d7e Add Privacy title to widget for screenreader access. r=fluent-reviewers,nina-py,bolsson
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 156 Branch

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

For more information, please visit BugBot documentation.

Flags: needinfo?(rhamoui)
Flags: needinfo?(rhamoui)

Verified that now the widget is read as "Privacy, article" on Firefox 156.0a1 (2026-08-20).

Status: RESOLVED → VERIFIED
Has STR: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: