These menus are normally owner-drawn commandbar buttons, which invoke an owner-drawn listbox underneath with the menu items hence they only show up as a WinObject. There are several ways to overcome the problem...
a. You could use virtual objects to map the menus, but the screen resolution and menu position musn't change.
b. Map the commandbar and use coordinate offsets to click on the menu items, defined as constants
c. Not sure if the .Net addin copes with these, but if it does use it
d. Use an intermediate dll to implement the IAccessible interface to the controls
e. If your organization develops the software, you can do what I have done and get them to implement a COM interface for the menus.
With our COM interface I only have to use a wrapper function which triggers the menu item specified.
There are probably a few more suggestions around.
I have already submitted a feature request to Mercury for an IAccessible addin, as several UI toolkits use this interface for testing. If you have maintenance, please request the same via support and add weight to the submission.
If you had to identify, in one word, the reason
why the human race has not achieved, and never
will achieve, its full potential that word would be "meetings".