Comment 1 by jteh (in reply to comment description) on 2011-09-15 07:22
Replying to kevinchao89:

Navigate to menubar, observe each item is identified as menu item, submenu item, clickable; all of this is very verbose, and all that is needed is menubar item;

Clickable is no longer spoken as of 47c7a02. However, "sub menu" is required to tell the difference between a menu item that opens a sub-menu and one that doesn't. "Menu item" is spoken so you know what the control is. I guess you could argue these should only be encountered within menu bars or menus, so this doesn't need to be spoken.

ENTER on one of the menu items, navigate around, and observe that same level of verboseness exist within each menu item;

When you pressed enter on the item, it should have switched to focus mode. Menu bars really are intended to be used in focus mode, not browse mode.

When using LEFT/RIGHT ARROWS to go from menu items to mmenu items, NVDA should always speak which menu item is being expanded and which item has focus, which it partially does, but does not always speak menu item that is expanded.

NVDA doesn't speak the new sub-menu when switching between them in desktop applications either. Doing so tends to cause way too much verbosity in various places. In any case, I'd argue this is consistent with current behaviour elsewhere, unless I'm misunderstanding you.

@jcsteh Assuming that the reported issue still occurs with the latest version of Firefox and elsewhere, your #1756 (comment) seems to be providing cogent justification against this ticket. Could you please clarify if this implies a wontfix, or am I misunderstanding something?

The outstanding issue here is that "menu item" gets reported in browse mode, but it's superfluous, since this should be clear from the reported "menu bar" or "menu". We also don't need to report "check menu item". This would make browse mode consistent with focus mode.

P3, because it's annoying but doesn't break functionality and isn't widely reported as problematic by users. Not a candidate for 2017webfix for the latter reason.

We'd need to report checkMenuItems. How else will we know if it's checked/unchecked?

@feerrenrut, any updates on this topic? There are several issues on github asking for a possibility to move reporting menu item after the label of the item. Or to suppress reporting menu item for browse mode as long as menubar and out of menu bar is reported. Hearing menu item in a menubar with many items seems to be annoying for many people. See for example different airline websites.

Update with NVDA 2019.3 Beta 2 and Firefox 72.0.1:
In focus mode, the item expanded and the currently focused option is alway reported correctly.
In browse mode, the verbosity is still high, but menu item sub menu is only reported if the menu item has other menu items in it. So this is ok from an user perspective because then I know that I can expand that menu item.
In browse mode expanding the menu item submenu is always reported correctly.
Clickable is only reported when expanding a menu item sub menu and entering the sub emnu. It is also only reported on the last item of the submenu.

In my view, the only point that still remains to be discussed is to suppress the reporting of "menu" on every menu item after entering the menu itself. NVDA already reports "menu bar" when entering and leaving it. So reporting only "item" for every menu item in browse mode would be enough in my view.
But sub menu and clickable should still be reported because this is useful information for an user.