Table navigation in word with UIA is verbose and omits cell coordinates

[Neurrone]

Steps to reproduce:

1. Create a table in word with use of UIA enabled in NVDA's advanced settings.
2. Try using the tab key and the arrow keys to navigate through the table.

Actual behavior:

1. Cell coordinates are not announced at all, making table navigation practically impossible to use with UIA. This happens with both use of tab / shift-tab, and the use of the arrow keys to move between cells.
2. When moving focus from a cell to another when the selection changes, the occurance of the previous cell's contents being unselected is spoken, as well as the new cell's contents being selected. This is not as severe as the first problem as you can skip those announcements by interrupting speech, but is pretty verbose.

Expected behavior:

1. Cell coordinates are spoken as you move through the table by any means (tab or arrow keys)
2. Suppression of the text selection events which is causing excessive verbiage

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

alpha-21524,7b92e442

Windows version:

Windows 10 2004

Name and version of other software in use when reproducing the issue:

Word 16.0.13426.20270

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

Yes, behaviour is unchanged

If addons are disabled, is your problem still occuring?

Yes

Did you try to run the COM registry fixing tool in NVDA menu / tools?

No

[zstanecic]

Hi! I recall this being a duplicate of something in the past. I’ve reported this last year. From: Dickson Tan <notifications@github.com> Sent: Monday, December 21, 2020 9:22 AM To: nvaccess/nvda <nvda@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [nvaccess/nvda] Table navigation in word with UIA is verbose and omits cell coordinates (#11956) Steps to reproduce: 1. Create a table in word with use of UIA enabled in NVDA's advanced settings. 2. Try using the tab key and the arrow keys to navigate through the table. Actual behavior: 1. Cell coordinates are not announced at all, making table navigation practically impossible to use with UIA. This happens with both use of tab / shift-tab, and the use of the arrow keys to move between cells. 2. When moving focus from a cell to another when the selection changes, the occurance of the previous cell's contents being unselected is spoken, as well as the new cell's contents being selected. This is not as severe as the first problem as you can skip those announcements by interrupting speech, but is pretty verbose. Expected behavior: 1. Cell coordinates are spoken as you move through the table by any means (tab or arrow keys) 2. Suppression of the text selection events which is causing excessive verbiage System configuration NVDA installed/portable/running from source: Installed NVDA version: alpha-21524,7b92e442 Windows version: Windows 10 2004 Name and version of other software in use when reproducing the issue: Word 2016 16.0.13426.20270 Other information about your system: Other questions Does the issue still occur after restarting your computer? Yes Have you tried any other versions of NVDA? If so, please report their behaviors. Yes, behaviour is unchanged If addons are disabled, is your problem still occuring? Yes Did you try to run the COM registry fixing tool in NVDA menu / tools? No — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#11956> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVCDE2PI4BA25DUNTAL7WLSV4ATHANCNFSM4VD4FDMA> . <https://github.com/notifications/beacon/ACVCDEZBEJY354SPXMHWQWDSV4ATHA5CNFSM4VD4FDMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4LQDHSAA.gif>

[michaelDCurran]

The first point was fixed in #12731 .
If the second point is still a problem, please open a separate issue.

[Neurrone]

Thanks @michaelDCurran.

The second is still an issue for me, and I've created #12998 to track that separately.