Closed Bug 1834397 Opened 11 months ago Closed 11 months ago

Read status accessible name for screen reader users is not respecting columns visibility

Categories

(Thunderbird :: Folder and Message Lists, defect, P2)

Thunderbird 115

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1825993

People

(Reporter: pvagner, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access, regression, Whiteboard: [Supernova3p])

+++ This bug was initially created as a clone of Bug #1825864 +++

When I use the arrow keys to navigate through the unread or read messages in the message list, the status "Unread" or "Read" is always reported as a part of the message list item accessible name even if the read status column is not visible.

Steps to reproduce

  1. Reconfigure the message list in a way so status column is visible and read status is not visible
  2. Make sure that the message list contains both unread and read messages.
  3. Navigate through the message list using the arrow keys.

Result

The messages are announced, and message list item is containing text of both columns status as well as read status eventhough list is configured not to show read status.

Expected

Accessible name presentation for screen reader users should respect the user settings including column visibility and read status should not be read in case the read status column is not visible.

Note: The feature has been recently enhanced as a result of the bug 1825864. Now the default setup is great for casual users but screen reader users wishing to use status column instead of read status are not able to disable the read status presentation.

Blocks: sn-msglist
Severity: -- → S3
Component: Disability Access → Folder and Message Lists
Keywords: access, regression
Priority: -- → P2
Whiteboard: [Supernova3p]
See Also: → 1825993

I suspect this is very much the same symptom that is affecting bug 1825993.
I think I know what's going on. I'll investigate, thanks for the report

Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → RESOLVED
Closed: 11 months ago
Duplicate of bug: 1825993
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.