Open Bug 1842024 Opened 1 year ago Updated 1 year ago

Unmutting the sound using keyboard navigation shows a small inconvenience

Categories

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

Desktop
All
defect

Tracking

()

Accessibility Severity s3
Tracking Status
firefox-esr102 --- disabled
firefox-esr115 --- disabled
firefox115 --- disabled
firefox116 --- affected
firefox117 --- affected

People

(Reporter: danibodea, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

When the user navigates PiP using the keyboard, focuses the volume slider, decreases the volume to 0 (left or down arrows), then focuses the unmute button (SHIFT+TAB to go backward) and taps ENTER, he will notice that the PiP's buttons will disappear, but the sound is not unmuted. If he taps ENTER again, the sound will finally unmute.

Found in

  • Beta v116.0b1

Affected versions

  • Nightly v117.0a1
  • Beta v116.0b1

Tested platforms

  • Affected platforms: all
  • Unaffected platforms: none

Steps to reproduce

  1. Play any video (YT, Netflix, Disney...)
  2. Launch the PiP.
  3. Use keyboard navigation to focus the PiP's volume slider (TAB).
  4. Decrease the volume using keyboard navigation (DOWS ARROW).
  5. Focus the UNMUTE button (SHIFT+TAB).
  6. Tap ENTER to unmute the sound.
    Expected result
  • The sound unmutes.
    Actual result
  • The PiP's buttons hide, but the sound does NOT unmute.
  1. Tap ENTER again.
    Actual result
  • The sound unmutes.

Regression range

  • Not a regression.

:danibodea, if you think that's a regression, could you try to find a regression range using for example mozregression?

Accessibility Severity: --- → s3

The severity field for this bug is set to S4. However, the accessibility severity is higher, .
:mhowell, could you consider increasing the severity?

For more information, please visit BugBot documentation.

Flags: needinfo?(mhowell)
Severity: S4 → S3
Flags: needinfo?(mhowell)
Priority: -- → P3
Blocks: 1838618
You need to log in before you can comment on or make changes to this bug.