1921037 - The sidebar in the viewer is hard to reach with the <TAB> key

Status: NEW

(Firefox :: PDF Viewer, defect, P3)

Description

[Calixte Denizet (:calixte)]

Attach (recommended) or Link to PDF file here:

Steps to reproduce the problem:

1. Open a pdf like https://github.com/mozilla/pdf.js/blob/master/test/pdfs/tracemonkey.pdf
2. Reach the toggle sidebar button (on the top left of the viewer)
3. Use <tab> to go on the first button in the sidebar.

In Edge, <tab> from the toggle button lets the focus moving on the first button in the sidebar.
In Chrome, <tab> moves the focus on the toolbar and then on the sidebar.

:ayeddi, what do you think we should do there ?

Comment 1

[Anna Yeddi [:ayeddi]]

I think, we could go both ways, but visually it seems that the Chrome approach would be more fitting: the sidebar itself is kind of opens on the second row of controls (after the toolbar), plus, I assume, toolbar buttons may be used more often than the sidebar (this is why the sidebar is offered to be collapsed/expanded).

Right now, the sidebar controls are included in the focus order before their toggle. Marking it as access-S3 for the inconsiderate focus order.

I think, if we could move them in the DOM to be after the toolbar itself and add the aria-controls on the sidebar toggle that would be pointing to the ID of sidebarContainer (because the sidebar is not an accessibility child of it's toggle.

Comment 2

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

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

For more information, please visit BugBot documentation.

Comment 3

[Calixte Denizet (:calixte)]

Aligning with a11y severity, so I'm setting the severity to S3.