Re: UAIG Menu events

Rich,

Is there something implied (or explicit that I have missed) in the spec 
that menus must close? Wouldn't the spec support a persistent menu, i.e., 
a list of links that is navigated with arrow keys? This is distinctly 
different from a listbox in presentation. The user would enter the menu 
with tab and leave with tab so a focus change would end menu mode.

A mega menu pattern we have used is to put a series of persistent menus, 
along with other widgets in a dialog. Each of the menus in the mega menu 
dialog is persistent. And, if the user tabs to a search field or some 
information that is in the dialog, the AT would not be in menu mode. This 
enables a very efficient keyboard experience since each menu is only one 
tab stop.

Matt King
IBM Senior Technical Staff Member
I/T Chief Accessibility Strategist
IBM BT/CIO - Global Workforce and Web Process Enablement 
Phone: (503) 578-2329, Tie line: 731-7398
mattking@us.ibm.com



From:   Richard Schwerdtfeger/Austin/IBM@IBMUS
To:     Joseph Scheuhammer <clown@alum.mit.edu>, 
Cc:     Cynthia Shelly <cyns@exchange.microsoft.com>, W3C WAI Protocols & 
Formats <public-pfwg@w3.org>, Alexander Surkov 
<surkov.alexander@gmail.com>
Date:   10/30/2013 01:57 PM
Subject:        Re: UAIG Menu events



It should be up to the author to close the menu when the user moves focus 
away. 

Rich


Rich Schwerdtfeger

Joseph Scheuhammer ---10/30/2013 02:39:59 PM---On 2013-10-30 3:29 PM, 
Richard Schwerdtfeger wrote: that works.  With that in mind, here's the 
lates

From: Joseph Scheuhammer <clown@alum.mit.edu>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS, Joseph Scheuhammer 
<clown@alum.mit.edu>, 
Cc: Cynthia Shelly <cyns@exchange.microsoft.com>, W3C WAI Protocols & 
Formats <public-pfwg@w3.org>, Alexander Surkov 
<surkov.alexander@gmail.com>
Date: 10/30/2013 02:39 PM
Subject: Re: UAIG Menu events



On 2013-10-30 3:29 PM, Richard Schwerdtfeger wrote: 
that works.

With that in mind, here's the latest.  Still waiting on Cynthia for advice 
about how to combine rows 5 and 6.

However, the fact that the old text MSAA text for row 6 said, "clear menu 
mode", the implication is that the user has moved away from the menu bar, 
and not simply moved focus out of a menu, leaving it open.
Scenario
MSAA
Microsoft UIA
Mac OS X
Menubar is currently not active, and user moves focus to the menubar from 
elsewhere thereby activating it. As a result, a menuitem in the menubar is 
focused. 
Menubar must a DOM parent of the menuitems or one defined by aria-owns. 
Activate the menu bar and fire EVENT_SYSTEM_MENUSTART on the accessible 
object for the menubar.
MenuModeStartEvent on the accessible object for the menu
AXMenuOpenedNotification
Focus a menu item while menubar is activated.
EVENT_OBJECT_FOCUS
AutomationFocusChangedEvent
AXMenuItemSelectedNotification
Menu popup made visible (menu is opened). 
Should only be fired once until the menu is closed and opened again.
EVENT_SYSTEM_MENUPOPUPSTART
MenuOpenedEvent, then a focus event on a menuitem
AXMenuOpenedNotification
Menu popup hidden (menu is closed).
EVENT_SYSTEM_MENUPOPUPEND once only for accessible menu object and only if 
EVENT_SYSTEM_MENUPOPUPSTART was fired for it.
MenuClosedEvent
AXMenuClosedNotification
All menus closed, and user moves focus away from menubar; menubar is 
deactivated.
EVENT_SYSTEM_MENUEND on the menubar; deactivate the menubar
MenuModeEndEvent
AXMenuClosedNotification
Focus moved out of menu I CAN'T RELATE THIS SCENARIO TO ANY OF ALEX's 5 
SCENARIOS.
EVENT_SYSTEM_MENUPOPUPEND, then EVENT_SYSTEM_MENUEND and deactivate the 
menubar
MenuClosedEvent, then MenuModeEndEvent
AXMenuClosedNotification


-- 
;;;;joseph.


'A: After all, it isn't rocket science.'
'K: Right. It's merely computer science.'
            - J. D. Klaun -