"focused" should not be reported when pressing NVDA+tab

[CyrilleB79]

Steps to reproduce:

This is just an example but it happens on any focused object.

• Open NVDA menu
• Press NVDA+tab

Actual behavior:

NVDA is too verbose. It reports "focused". In the case of the script reporting the focus, it is a completely unuseful information.

Expected behavior:

NVDA should not report "focused" when using NVDA+tab since it is expected.

NVDA logs, crash dumps and other attachments:

N/A

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

2024.4.1rc1

Windows version:

Windows 10 22H2 (AMD64) build 19045.5011

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

N/A

Other information about your system:

N/A

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.

No, but probably the same.

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 tested, unrelated.

[Adriani90]

I think NVDA reports everything right, see following scenarios:
Scenario 1:

1. Use system focus to focus a menu item
2. Use the navigator to move the NVDA cursor to another place, press nvda+tab.

Scenario 2:

1. In a browser, use focus mode to move system focus to a link
2. In browse mode, navigate to another place
3. Press nvda+tab

In both scenarios we moved a cursor that did not impact the system focus, still NVDA+tab was able to report what is focused with system focus.
I can imagine in some cases for advanced users this is too much verbosity, but for beginners this info is important when working with these navigation concepts.

I can imagine that dropping the reporting of "focused" would be something suitable for an additional verbosity profile when fixing #46.

[CyrilleB79]

My point is that pressing NVDA+Tab, NVDA will always report focused state, since NVDA+Tab reports the focus. This is too much verbosity because when I request to report the focus, I'll necessarily get a focused object as feedback. Said otherwise, there is no case where pressing NVDA+Tab would not report the focused state. Thus, this information is not needed.

To take another example that is well implemented instead in NVDA. When you move with upArrow or downArrow in a list view, NVDA does not report selected, because everyone expects that the selection be moved with arrows and thus, the object being reported after the move will always be selected.

@Adriani90 I do not understand why the examples you have provided would illustrate the need of a different expected behaviour. Could you be more specific?