Open Bug 1833715 Opened 11 months ago Updated 7 months ago

Message list column picker: (De)selecting a column is not communicated to screen readers (checked vs. unchecked)

Categories

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

Thunderbird 115

Tracking

(Accessibility Severity:s2)

ASSIGNED
Accessibility Severity s2

People

(Reporter: ali-savas, Assigned: elijmitchell)

References

(Blocks 1 open bug)

Details

(Keywords: access, Whiteboard: [Supernova3p])

If I want to check or uncheck a certain column, the status "Checked" or "Not checked" is not communicated to me by the screen reader. I can reproduce this with JAWS as well as with NVDA.

Steps to reproduce

  • In the message list, press Shift+TAB once and activate the "Select columns to display" button. Note, the English name may differ.
  • Use the arrow keys to select any column you want to check or uncheck and confirm with Enter. Repeat a few times on the same entry.

Result

It is not announced whether the entry was checked or unchecked.

Expected

The screen reader should announce "Checked" or "Not checked".

Keywords: access

Thanks Ali.
Confirming for Daily 115.0a1 (2023-05-17) (64-bit), Win10 (tested with NVDA).

Fortunately, when you navigate to a column in column picker, it will announce its status (which would be a clumsy workaround for this bug).
But then, changing the column status from checked to unchecked or vice versa using Enter is indeed not announced at all.

Blocks: sn-msglist
Severity: -- → S3
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Column selection: Statuses "Checked" or "Not Checked" are not communicated to the screen reader → Message list column picker: (De)selecting a column is not communicated to screen readers (checked vs. unchecked)
Whiteboard: [Supernova3p]
Assignee: nobody → elizabeth
Status: NEW → ASSIGNED
Assignee: elizabeth → nobody
Status: ASSIGNED → NEW
Accessibility Severity: --- → s2
Assignee: nobody → elizabeth
Severity: S3 → S2
Status: NEW → ASSIGNED
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.