Open Bug 1954249 Opened 5 months ago Updated 5 months ago

the tab key does not behave as expected when navigating with NVDA

Categories

(Thunderbird :: Message Reader UI, defect)

Thunderbird 128
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: r.cavanaugh, Unassigned)

References

Details

(Keywords: access)

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

Steps to reproduce:

  1. Using NVDA, open a message with multiple links. Navigate by any means to the first link, whether that be with the tab key, the arrow keys, or by reading a message and stopping speech at the first link with control.
  2. Press control+home to go to the top of the message.

Actual results:

If you've followed both steps above, you will notice two things:

  1. The tab focus will remain on the focused link, despite having pressed control+home to move to the top of the message.
  2. Additionally, your context menu will display options pertaining to the link, not to the message. If you're in a message with many links, this is an even more observable problem, as your tab focus will be on whatever link you focused on last, not where you think the cursor is. For example, you are viewing a message with five links total, and you're on link #3. Go up to the top of the message with control+home. First, use your context menu to try to move the message to another folder. The context menu will be for that of a link, not the message. Pressing tab here, you will hear link #4, not link #1. Pressing your arrow keys does work as expected here.

Expected results:

When pressing control+home, all focus elements should return to the top of the message, and tabbing should place you on the first link in the message, as happens in Firefox and all other applications.

Keywords: access

It looks like this has been significantly improved on in 128.9. When I tab through things, I am now placed where I expect to be, but sometimes the context menu still gives options for a link when no link has focus.

You need to log in before you can comment on or make changes to this bug.