Open Bug 1819599 Opened 2 years ago Updated 11 months ago

NVDA reads the buttons from PIP window only at tab action not at hover.

Categories

(Toolkit :: Picture-in-Picture, defect)

Product:
Toolkit
Component:
Picture-in-Picture
Version:
Firefox 112
Platform:
Desktop
Windows
Type:
defect

Tracking

()

Project Flags:
Accessibility Severity s4
Tracking Flags:
Tracking Status
firefox-esr102 --- affected
firefox111 --- affected
firefox112 --- affected

People

(Reporter: mchiorean, Unassigned)

Details

(Keywords: access)

Found in

  • 112.0a1 Nightly (20230228085339)

Affected versions

  • 108.0a1(20221108213602)
  • 112.0a1 (20230220165121)
  • 102.8.0esr (20230214011352)

Tested platforms

  • Affected platforms: Win10, Win11, Win7, Ubuntu22.
  • Unaffected platforms: -

Steps to reproduce

  1. Open a youtube video with subtitles enabled.
  2. Open PIP windows and NVDA.
  3. On PIP windows hover each button with NVDA.

Expected result

  • Text should be read by NVDA at hover.

Actual result

  • Text is not read. Text is read only if tab action is performed on each button, or if the button is pressed. Also the buttons are not read by hovering the cursor (or the timelapse).

Regression range

  • Don’t think it is a regression as the subtitle buttons were recently added and issue also reproduces on older versions like 108.0a1(20221108213602).
Severity: -- → S3
Has STR: --- → yes
status-firefox111: --- → affected
status-firefox-esr102: --- → affected
Keywords: access
Whiteboard: [access-s4]

:Jamie, could this be a hittesting problem?

Flags: needinfo?(jteh)

Do these buttons have visible text or are they icons with a11y labels/tooltips? If they don't have visible text always, NVDA mouse tracking will not read the text, which is a known issue with NVDA mouse tracking.

Flags: needinfo?(jteh)

It's unlikely to be a hit testing problem because I think the PiP UI runs in our parent process, not the content process (so not impacted by caching).

Accessibility Severity: --- → s4
Whiteboard: [access-s4]

If the PiP image buttons are properly labeled (which I think is the case), this is likely the NVDA bug as Jamie has mentioned in #c2.

What we could do to make the user experience better is either:

  1. to add an on-screen text next to color option circles, so there is an on-screen text (that is included in the option markup) - this should be announced by the NVDA.
  2. to add an invisible <span> in the button as Calixte offered in the bug 1886964#c1 and in the attached patch. This would also work as an accessible name source for the button.
You need to log in before you can comment on or make changes to this bug.