1852957 - [meta] Improve Unread status information for screen readers

Status: NEW

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

Description

[Ali Savas]

Personally, the screen reader's constant announcement of "Read" before every message I read annoys me and I don't need the announcement, so I wanted to disable the "Status Read" column and enable the "Unread" column instead. My expectation was that the screen reader would announce "Unread" for unread messages and simply read the message for read messages without announcing "Unread" or "Read". However, this is not the case. If I disable the "Status Read" column and enable the "Unread" column instead, the screen reader does not tell me "Unread" for unread messages.

It's also not a good idea to generally not have the "Read" status announced, as there will certainly be people who want this announcement. Therefore, I suggest that if the "Unread" column is enabled, to have the screen reader also announce "Unread".

Steps to reproduce

1. Disable the "Status Read" column and enable the "Unread" column instead.
2. Arrange the column so that it is as the first column.
3. Go to the message list with TAB and select an unread message with the arrow keys.

Result

The screen reader does not say "Unread".

Expected

The screen reader should announce "Unread" before each unread message.

Comment 1

[Elizabeth Mitchell]

I am confirming this bug. If Read Status is unchecked from the columns in the message table, then read/unread status is not read out by the screen reader.

The "Unread" column is not a true/false column. It displays the number of unread messages, which is unclear. If the message is a single message and unread, this number will be 1. If the message is a thread or messages, the number will be the number of unread messages. There should be more context to explain this is the number of unread messages in a thread.

I do think users should be able to customize the columns as they like so that they hear the information that they want to hear.

This is what I propose based on this information:
If the "Read Status" is enabled, announce "Unread" when an item is unread. Do not announce "Read" if the item has been read.
If the "Unread" column is enabled, announce the number of unread messages. If it is a single message, not a thread, simply read off "Unread."

Comment 2

[Ali Savas]

If the "Read Status" is enabled, announce "Unread" when an item is unread. Do not announce "Read" if the item has been read.
If the "Unread" column is enabled, announce the number of unread messages. If it is a single message, not a thread, simply read off "Unread."

For all I care, you could do it that way. However, there may be a few users who also want to hear "Read", which makes no sense in my opinion.

Comment 3

[Elizabeth Mitchell]

Thanks for your feedback, Ali.

Comment 4

[Elizabeth Mitchell]

Comment from Mastodon user, Simon Jaeger:

I notice that in the new Thunderbird, when a message is read, the list item for the message will have the word "read" appended to it. This seems like a regression from older Thunderbird where it would only announce read status when the message was unread. The absence of the word "unread" was enough of a clue. This matters because it significantly slows down quick navigation of many messages in a list. I can't skim through messages quickly by sender anymore because I'm always pausing to wait for the word "read". Was this a deliberate decision or just a result of the redesign? Is there any openness to changing it? If you'd rather not engage here, do you mind telling me where i could go to ask about it?

I responded to the user. I also think we should move unread earlier in what is announced so users don't have to wait. Ali also suggested

The screen reader should announce "Unread" before each unread message.

Comment 5

[Elizabeth Mitchell]

I am making this a meta bug so that we can split out the different improvements needed.

Comment 6

[Elizabeth Mitchell]

This requires design. I'm un-assigning myself from this work for now, as I am not actively working on this yet.

Comment 7

[Elizabeth Mitchell]

After thinking this over and looking into how our code is working with the screen readers, here are some of the things that can make this better. This applies to the Table View of the message list.

• Make it obvious when a message is unread. Move the "Unread" information at the start of what is read for a message.
• If a message has already been read, do not include the word "Read" in the message row's aria-label information.
• Make the unread or read status information available in the row during cell navigation. If an individual wants to know whether the message is unread or read, this information can be made available directly while navigating the row's contents.

Bug 1860561 requires more thought, but these other changes should help considerably.

Comment 8

[Elizabeth Mitchell]

I'm working on bug 1860562 to move the Unread information earlier.

There are two approaches we could take. Any feedback is welcome. I've posted feedback on my patch and am sharing what I wrote here.

There are two approaches to getting the message row in Table View's information to read off "Unread" early.

We can switch the order of the default columns. The order of what is read for the aria-label for the message will then reflect Unread directly before the subject. However, if users change the order of the columns, they won't always hear Unread first. Users will also need to reset their message columns order to hear this new order. The advantage to this approach is that the order of what is read inside the aria-label is customizable if Unread is not the most important information.

A second approach is to always include "Unread" as the first item read or one of the first items read. The advantage is that the default order of the columns would not need to be changed. The con is that users won't be able to adjust this setting (Unread being read first). But based on user feedback, having this information available is extremely helpful for navigating the message list with a screen reader or other assistive device.

I am leaning towards using the second approach, which allows Unread to be read off first. But users can customize the order of the columns however they like and it does not affect Unread being read first or close to first for each message when navigating the message list.

Comment 9

[Ali Savas]

I prefer the first approach. This way, every user can customize this information as they need it. This would also reflect the behavior of the columns, as Thunderbird has always done. Until Thunderbird 115, it was possible to move the "Unread" information as well.

Comment 10

[Elizabeth Mitchell]

(In reply to Ali Savas from comment #9)

I prefer the first approach. This way, every user can customize this information as they need it. This would also reflect the behavior of the columns, as Thunderbird has always done. Until Thunderbird 115, it was possible to move the "Unread" information as well.

Thank you Ali. I have a patch for this work, so I will move the patch forward this week.