Closed Bug 1589862 Opened 6 years ago Closed 2 years ago

Action buttons in the message preview pane for a message not reachable via keyboard

Categories

(Thunderbird :: Disability Access, defect, P3)

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1816784

People

(Reporter: k.kolev1985, Assigned: aleca)

References

(Depends on 1 open bug)

Details

(Keywords: access)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

  1. Launch a screen reader like NVDA or Narrator.
  2. Launch Thunderbird 68.
  3. Make sure that the message preview pane is enabled.
  4. Navigate to/select a folder containing a few messages.
  5. Select a message from the list, so it appears in the message preview pane.
  6. Use the TAB key to navigate between the controls in the headers pane.

Actual results:

The action buttons (e.g. "Reply", "Forward", "Reply to all", etc.) are not reachable via keyboard navigation (TAB or Shift+TAB).

Expected results:

The action buttons (e.g. "Reply", "Forward", "Reply to all", etc.) should be reachable via keyboard navigation (TAB or Shift+TAB) in the headers pane of the message preview pane.

Alex and Jean-Philippe, there's more and more.

Flags: needinfo?(jpmengual)
Flags: needinfo?(aarnaud)

Hi,

We choosed, so far, to focus on regressions instead of improvements. This bug is confirmed, because the action buttons are never accessible (reading or writing a message). All the toolbar is not, actually.

On the other hand, while I wih they are in contexts such as the columns headings in the message list or calendar events list (to sort the messag, re-order the columns), I think the workaround is relatively easy for actions in message. The user has 3 options: keyboard shortcuts (ctrl-r, l, a, etc), the Message menu, and the context menu (shift-f10 or Menu key). So I am not sure working on this is mandatory as the user can do the actions with many othr workarounds. Tell us the impossible actions, it will be likely easier to implement a shortcut or a menu entry for them.

Regards

Flags: needinfo?(aarnaud)

Thanks again.

Flags: needinfo?(jpmengual)

(In reply to Jean-Philippe MENGUAL from comment #2)

Hi,

We choosed, so far, to focus on regressions instead of improvements. This bug is confirmed, because the action buttons are never accessible (reading or writing a message). All the toolbar is not, actually.

On the other hand, while I wih they are in contexts such as the columns headings in the message list or calendar events list (to sort the messag, re-order the columns), I think the workaround is relatively easy for actions in message. The user has 3 options: keyboard shortcuts (ctrl-r, l, a, etc), the Message menu, and the context menu (shift-f10 or Menu key). So I am not sure working on this is mandatory as the user can do the actions with many othr workarounds. Tell us the impossible actions, it will be likely easier to implement a shortcut or a menu entry for them.

Regards

Thanks for your reply.

Actually, although I use the message pane in which those buttons are located, I don't use those action buttons. Normally I use the corresponding keyboard commands or the context menu. But I've decided to report it anyway, because I've noticed the bug while reproducing some other bugs.

So, this issue/bug could be determined as "low priority".

Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
See Also: → 1589859

Magnus do you agree with the priority? (and related bugs?)

Flags: needinfo?(mkmelin+mozilla)
See Also: → 1589861
See Also: → 1589863

Seem not too bad, especially since - as mentioned - keyboard users are likely to pick up on the keyboard shortcuts for these actions and use those.

Flags: needinfo?(mkmelin+mozilla)
Keywords: access
Priority: P2 → P3
Assignee: nobody → alessandro
Severity: normal → S3

We're addressing this in bug 1816784, which doesn't rely on an HTML toolbar

Status: NEW → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1816784
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.