Closed Bug 1659467 Opened 1 year ago Closed 1 year ago

Keyboard navigation not possible because new modal is not focused upon launch

Categories

(Toolkit :: Printing, defect)

Firefox 81
Desktop
All
defect

Tracking

()

RESOLVED FIXED
81 Branch
Tracking Status
firefox81 --- fixed

People

(Reporter: vlucaci, Assigned: mstriemer)

References

(Blocks 2 open bugs)

Details

(Keywords: access, Whiteboard: [access-s2])

Attachments

(1 file)

Affected versions

  • 81.0a1(20200817093723)

Affected platforms

  • Ubuntu 18.04
  • macOS 10.15.6
  • Windows 10x64
  • Windows 10aarch64

Steps to reproduce

  1. Launch FF.
  2. Trigger the new Print UI modal.
  3. Press tab to navigate options with keyboard.

Expected result

  • New printing modal is focused as soon as it is opened and the user can navigate all the modal's options.

Actual result

  • New UI modal is not focused and the Tab keyboard navigated the options of the page in the background.

Suggested Severity

  • Seeing as how most of the users navigate the modal via mouse, and the fact that that the modal can still be interacted with keyboard(using Shift+Tab instead or selecting an option via mouse first) I see this issue as an S3.

Regression range

  • Not a regression

Additional notes

  • Screen cast of the issue:
Keywords: access

This is intermittent for me; it sometimes gets focus and other times doesn't. However, this is pretty serious for screen reader users and potentially users of other accessibility tools. Screen reader users won't even know the print modal has appeared and won't know how to get to it.

Blocks: 1657994
Whiteboard: [print2020_v81] → [print2020_v81] [access-s2]

(This should be fixed by the third patch on bug 1653317 so removing the [print2020_v81] whiteboard tag for easier tracking.)

Whiteboard: [print2020_v81] [access-s2] → [access-s2]

Jamie, can you see on a more recent nightly if this is fixed now bug 1653317 is fixed?

Flags: needinfo?(jteh)

As I noted in comment 1, this was always intermittent for me, so I can't be certain. That said, I've tried in quite a few different scenarios and repeated attempts and I can no longer reproduce this.

Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(jteh)
Resolution: --- → FIXED
Assignee: nobody → mstriemer
Depends on: 1653317
Target Milestone: --- → 81 Branch
You need to log in before you can comment on or make changes to this bug.