-
-
Notifications
You must be signed in to change notification settings - Fork 734
Description
Brief summary
When aria-label is provided to label an empty column header cell or to overwrite the existing string in it, NVDA ignores the explicit accessible name and either announcing the on-screen text of the cell or not announcing anything at all (for empty header cells)
Steps to reproduce
- Open
data:text/html,<table><tr><th scope="col" aria-label="First">Visible</th><th scope="col" aria-label="Second hidden"></th></tr><tr><td>foo</td><td>bar</td></tr></table> - With NVDA, navigate between the first and second columns and observe the announcement
Actual behavior
An NVDA is announcing the following:
- For the first column with an on-screen string "Visible" and
aria-label="First", the "Visible" is announced (column 1, Visible) - For the second column that is empty and has
aria-label="Second hidden", nothing is announced (column 2)
Expected behavior
An NVDA should be announcing the column header's accessible names (that are calculated as "First" and "Second hidden", per Accessibility tree inspection on both Firefox and Chrome):
- For the first column with an on-screen string "Visible" and
aria-label="First", the "First" should be announced (column 1, First) - For the second column that is empty and has
aria-label="Second hidden", the "Second hidden" should be announced (column 2, Second hidden)
NVDA logs, crash dumps and other attachments
No response
NVDA type
installed copy
NVDA version
2025.3.2.53588
Have you tried any other versions of NVDA? If so, please report their behaviors.
No response
Windows version
Windows 11 Pro 25H2
Name and version of other software in use when reproducing the issue
Firefox 146.0 (release) and Chrome 143.0
Other information about your system
No response
Does the issue still occur after restarting your computer?
I have restarted my computer and the issue still occurs
If NVDA add-ons are disabled, is your problem still occurring?
I have restarted NVDA with add-ons disabled and the issue still occurs
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
I have run the COM Registration Fixing Tool and the issue still occurs