[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)
Tracking
()
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
- Reach the Privacy widget in a new tab page
- 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
- The issue with sound can be seen in the following attachment
Comment 1•3 months ago
|
||
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:
-
"article" with no name. The root is a bare
<article>with onlyclassName/ref— no heading and noaria-label/aria-labelledby(Privacy.jsx#505-519)..privacy-title-wrappercontains only the context-menu button, so VO announces an unnamed article. Peers name theirs with visible title text (Stocksnewtab-stocks-widget-title, Crossword<h3>, Weather<h3>{city}</h3>); Privacy has none, and nonewtab-privacy-widget-titlestring exists in newtab.ftl. -
"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-textlabels, 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. -
Unnamed menu button. The context-menu
moz-buttonhas nodata-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-labelledbyat it, ordata-l10n-idanaria-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 ownaria-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-buttonstring and set it on the menu button. - The existing
.privacy-count-numberaria-hidden+ visually-hidden.privacy-count-number-a11ypairing (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.
Updated•3 months ago
|
For other Widgets, what is the expected content type for the VO?
Updated•3 months ago
|
Updated•3 months ago
|
| Reporter | ||
Comment 3•3 months ago
•
|
||
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)?
The VO is reading but just not being specific about it, so not a launch blocker.
| Assignee | ||
Comment 5•3 months ago
|
||
Comment 7•2 months ago
|
||
| bugherder | ||
Comment 9•2 months ago
|
||
The patch landed in nightly and beta is affected.
:rhamoui, 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-firefox155towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•2 months ago
|
| Reporter | ||
Comment 10•2 months ago
|
||
Verified that now the widget is read as "Privacy, article" on Firefox 156.0a1 (2026-08-20).
Description
•