Open Bug 2017638 Opened 1 month ago Updated 16 days ago

The Voice over is stuck in a loop going backwards inside the Assistant response when a link is provided

Categories

(Core :: Disability Access APIs, defect)

Desktop
macOS
defect

Tracking

()

ASSIGNED
Tracking Status
firefox-esr140 --- disabled
firefox147 --- disabled
firefox148 --- disabled
firefox149 --- disabled

People

(Reporter: rdoghi, Assigned: morgan, NeedInfo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [genai][chat][qa])

Attachments

(2 files, 1 obsolete file)

Attached video LoopWithLink.mp4

Found in

  • Nightly 149.0a1 (2026-02-18)

Affected versions

  • Nightly 149.0a1 (2026-02-18)

Affected platforms

  • macOS

Preconditions
Enable Voice Over.

Steps to reproduce

  1. Reach the Smart Window.
  2. Ask the Assistant to summarize a page from mozilla.
  3. Use the VO commands to reach the first link from the Assistants response.
  4. Use VO + Left arrow in order to go back to the Top of the response.

Expected result

  • The Voice over should move to the top without issues.

Actual result

  • Users can only go forward with the VO + Right arrow or UP arrow, if they use VO + left arrow in order to go back they will be stuck in a loop.

Regression range
N/A

Accessibility Severity: --- → s2

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

For more information, please visit BugBot documentation.

Flags: needinfo?(edilee)
Whiteboard: [genai][chat] → [genai][chat][qa]
See Also: → 2027108
Attachment #9559353 - Attachment description: WIP: Bug 2017638 - The Voice over is stuck in a loop going backwards inside the Assistant response when a link is provided → Bug 2017638 - The Voice over is stuck in a loop going backwards inside the Assistant response when a link is provided
Assignee: nobody → jlewis
Status: NEW → ASSIGNED

Hi folks, I just tested with the patch above and am still able to reproduce the issue.
I can also reproduce it in web content with the following (copied from browser toolbox, apologies for the weird HTML comments):

data:text/html,<article>%20%20%20%20%20%20%20%20 <!--?lit$680726158$--><div class="message-assistant"><p>You're right! I apologize for the formatting error. Here are some non-profits similar to Mozilla that focus on internet health and advocacy, with their homepages linked inline as requested:</p><ul><li><p>The <strong>Electronic Frontier Foundation (EFF)</strong> is a leading nonprofit defending civil liberties in the digital world, focusing on free speech, privacy, and innovation. You can visit them at <a href="https://www.eff.org/">Electronic Frontier Foundation</a>.</p></li><li><p>The <strong>Internet Society (ISOC)</strong> works globally to ensure the internet remains a global, open, and accessible resource for everyone, focusing on policy, technology, and education. Their homepage is <a href="https://www.internetsociety.org/">Internet Society</a>.</p></li><li><p><strong>Access Now</strong> defends and extends the digital rights of users at risk around the world, addressing issues like internet shutdowns, surveillance, and content moderation. You can find them at <a href="https://www.accessnow.org/">Access Now</a>.</p></li><li><p><strong>The Tor Project</strong> develops and promotes free and open-source software and open practices to enable anonymous communication and resist surveillance. Their website is <a href="https://www.torproject.org/">The Tor Project</a>.</p></li></ul><p>These organizations, much like Mozilla, are dedicated to principles of openness, privacy, and user empowerment on the internet.</p></div>%20%20%20%20%20%20%20%20 <!--?lit$680726158$--><!--?lit$680726158$--><!--?-->%20%20%20%20%20%20 </article>

Because this reproduces in web content, I think we should migrate this issue to Disability Access APIs and try to fix it in the a11y engine. Please let me know if this sounds like the incorrect approach.

Severity: -- → S2
Accessibility Severity: s2 → ---
Component: Machine Learning: Frontend → Disability Access APIs
Keywords: access
Assignee: jlewis → mreschenberg
Attachment #9559353 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: