1866718 - Linked SVG <title> elements are not displayed in VoiceOver's Web Rotor

Status: RESOLVED WORKSFORME

(Core :: Disability Access APIs, defect)

Description

[kimberly.grey]

Attachment: svg-title-issue.html

Steps to reproduce:

1. Open the attached file (svg-title-issue.html) in Firefox on macOS.
2. Launch VoiceOver.
3. Navigate through the page's content using VoiceOver's controls (typically Ctrl + Opt + left/right arrows).
4. Listen to how each link is announced by VoiceOver.
5. Open the Web Rotor (typically Ctrl + Opt + U) and navigate to the Links section using the left/right arrows.
6. Observe how the links are displayed within the Rotor.

Actual results:

• All of the links on the page are announced as "A red circle with accompanying text"
• The Web Rotor displays the first three links as "with accompanying text", only the last link is "A red circle with accompanying text"
• When the Web Rotor list is navigated, each link is announced as "A red circle with accompanying text"

Expected results:

• All of the links on the page are announced as "A red circle with accompanying text"
• The Web Rotor displays all of the links as "A red circle with accompanying text"
• When the Web Rotor list is navigated, each link is announced as "A red circle with accompanying text"

My expectation would be that the text visually displayed in the Rotor should match what is being announced.

I also observed this issue in Safari, but not in Chromium-based browsers, making me think it may be in some way related to what the browser is exposing rather than VoiceOver itself.

The same issue is reported on the WebKit bug tracker here: https://bugs.webkit.org/show_bug.cgi?id=265321

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

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

For more information, please visit BugBot documentation.

Comment 3

[Morgan Reschenberg [:morgan]]

This seems fixed for me, closing as such. :nlapre did you work on some SVG stuff recently that could've affected this?

Comment 4

[Nathan LaPré]

Thanks for re-testing. Yeah, I think it might be a side effect of Bug 1877811, or a side effect of Bug 1878355, though I'm not sure. Either way, I'm glad it's fixed! Looks like we're now properly consulting the accessible node for the SVG element when calculating name from content for the links here.