I don't think there is a difference between a context menu and a pop-up
menu. There are no roles distinguishing between these two types of menus.
And even saying they are two types of menus is specious. Some menus emanate
from the menu bar, and some do not. But after that, they're all the same.
aloha, rob! i agree that a context menu and a popup are the same
thing -- something which will be reinforced by the upcoming editor's
draft of ARIA 1.0 where it is now categorically stated that a popup (as
in aria-haspopup=foo) is a context menu; consult:
Even though we could expose haspopup when we know there is a context
menu I'm not as sure we should since the way to invoke it is different.
The user would hear has popup, click (space bar) the widget and find no
popup (since it is a right click, menu key, shift-f10 that normally
invokes the
David,
When a page author creates their own context menu is when you should have
haspopup. The style gide says to use the same key strokes I believe. That
essentially would steal the strokes from the browser.
I am referring to has popup in content and not the browser mapping. You
don't generate
I think haspopup and hascontext should be differentiated when possible, as
Alex and David are suggesting. Even if the opened menus behave the same from a
screen reader point of view, the keystrokes/mouse invocation is different.
Also, there are visual appearance differences that can be
