MS Word: the default UI automation setting makes many NVDA's selection key strokes silent

[amirsol81]

Please take a look at the attached Word document. With the UI automation setting for MS Word in the Advanced pain of the settings dialog set to Default (Where necessary), NVDA remains silent after a short while as many selection/de-selection-related key strokes are pressed.

Steps to reproduce:

1. Make sure your UI Automation for Word in the Advanced pain of NVDA's Settings is set to Default (Where necessary. Also - preferably - make sure you're using the Web view in MS Word though this doesn't mostly matter.
2. Open the attached MS Word (DOCX) document.
3. Press Up/Down a couple of times. You may also press Control+PageDown a couple of times instead.
4. Try selecting text with SHIFT+Left, SHIFT+Right, SHIFT+Up, SHIFT+Down, SHIFT+Home and SHIFT+End.

Actual behavior:

Italian with Paul Noble.zip

NVDA's reporting of the selected/de-selected text is quite unreliable. Under most instances, it simply remains silent. It's worth mentioning that the only selection keystrokes which work consistently are Control+SHIFT+Left and Control+SHIFT+Right for word selection/de-selection. Setting Word's UI option to Always fixes the issue; however, it introduces glitches of its own.

Expected behavior:

NVDA should always read the selected/de-selected text, so remaining silent isn't an option!

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

Alpha 28569, and many recent alphas

Windows version:

Windows 11, Version 22H2 (OS Build 22621.1928)

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

Microsoft Word 2021, V16.08

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.

I haven't tried the official 2022.1 release, but many recent alphas are affected.

If NVDA add-ons are disabled, is your problem still occurring?

Yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Not done so