(Firefox) NVDA reads fieldset legends twice in browse mode (before and after "grouping")

[EricDunsworth]

When NVDA "enters" a fieldset, it usually reads the fieldset's legend, followed by "grouping", followed by the element that received focus.

That has the potential of causing the legend to be announced twice if the former and latter are one in the same:

• In Firefox, both browse + focus modes are affected. But in practice, the duplication is usually only encountered in browse mode (focus mode won't "land" onto legends unless something like tabindex="0" is used).
• By comparison, in Chrome, browse mode only reads the legend once (after "grouping"). Although duplication can still technically occur in focus mode if tabindex="0" is in play.

I was wondering whether something could be done to reduce the repetitiveness in Firefox's browse mode to be more in line with Chrome's behaviour?

CC @jcsteh

Steps to reproduce:

1. Visit this JS Bin sample in Firefox
2. Tab to the "Start" link
3. Press the down arrow key

Actual behavior:

Start  link
My legend  grouping    My legend

Expected behavior:

I'd reasonably expect to get either of the following behaviours...

• Read the legend before "grouping" (in line with focus mode in Firefox + Chrome):

  Start  link
  My legend  grouping
  

• Read the legend after "grouping" (in line with browse mode in Chrome):

  Start  link
  grouping    My legend
  

NVDA logs, crash dumps and other attachments:

N/A

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

2024.1 (2024.1.0.31547)

Windows version:

10.0.19045 Build 19045 (22H2)

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

• Firefox version: 127.0.1 (64-bit)
• Firefox Developer Edition version: 128.0b5 (64-bit)
• Chrome 126.0.6478.115 (Official Build) (64-bit)

Other information about your system:

N/A

Other questions

Does the issue still occur after restarting your computer?

Haven't tried

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

No

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

Yes (using factory default configuration - doesn't come with any add-ons)

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

Haven't tried