RE: Updated Menu Button Examples for APG

>>> I'd recommend setting focus to the first role=menuitem element after the menu button is activated. Otherwise it sounds like nothing has occurred to a non-sighted screen reader user.

As a matter of fact, active focus traversal is actually unfortunately the only mean some AT/UA combinations can detect that the associated popup has been opened. I would be very interested in a clear statement by the group what should be done by developer here by default.

Best Regards
Stefan


-----Original Message-----
From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com] 
Sent: Montag, 15. Februar 2016 20:15
To: Gunderson, Jon R <jongund@illinois.edu>; ARIA Working Group <public-aria@w3.org>
Subject: RE: Updated Menu Button Examples for APG

I'd recommend setting focus to the first role=menuitem element after the menu button is activated. Otherwise it sounds like nothing has occurred to a non-sighted screen reader user.

Also this comes into play for touch device users, where if focus is automatically set, it is possible to then swipe Left/Right on iOS for example to navigate between the menu items, but if focus is left on the button, you have to manually hunt for where the menu is located on the screen.

I'd also recommend adding a submenu example.

All the best,
Bryan



-----Original Message-----
From: Gunderson, Jon R [mailto:jongund@illinois.edu] 
Sent: Sunday, February 14, 2016 2:26 PM
To: ARIA Working Group <public-aria@w3.org>
Subject: Updated Menu Button Examples for APG


This example uses a button element as the menu button and demonstrates a menu of ³actions²:
https://rawgit.com/jongund/aria/master/practices/examples/menu-button/menu-
button-1.html

This example uses a a element as the menu button and demonstrates a menu of ³links²:
https://rawgit.com/jongund/aria/master/practices/examples/menu-button/menu-
button-2.html


Any comments about the operation, markup or the descriptions is welcome.

Jon

Received on Tuesday, 16 February 2016 08:13:25 UTC