E-mail List Archives
Re: Keyboard navigation using arrows only
From: Bryan Garaventa
Date: Sep 2, 2014 5:52PM
- Next message: Whitney Quesenbery: "Re: Accessible color and contrast for projected presentations"
- Previous message: Michael Tangen: "Re: Keyboard navigation using arrows only"
- Next message in Thread: Michael Tangen: "Re: Keyboard navigation using arrows only"
- Previous message in Thread: Michael Tangen: "Re: Keyboard navigation using arrows only"
- View all messages in this Thread
>When a link tag has the aria attribute aria-haspopup="true", JAWS actually announces the words "has submenu". So really, the arrow
is only of value to sighted users.
That's not true actually.
Regarding ARIA Menus, the Windows platform UI equivalent for this is documented at
http://msdn.microsoft.com/en-us/library/system.windows.controls.contextmenu.aspx
When an ARIA Menu is constructed strictly according to spec, It causes specific events to fire in the browser, which Assistive
Technologies then use to ensure accessibility by customizing feedback and behavior.
This process is documented in the UAIG, at
http://www.w3.org/TR/wai-aria-implementation/#mapping_events_menus
If you try the following demo using JAWS in IE or FF, you will see this in action:
http://whatsock.com/tsg/Coding%20Arena/ARIA%20Menus/Vertical%20(Internal%20Content)/demo.htm
-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Michael Tangen
Sent: Tuesday, September 02, 2014 4:40 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Keyboard navigation using arrows only
When a link tag has the aria attribute aria-haspopup="true", JAWS actually announces the words "has submenu". So really, the arrow
is only of value to sighted users.
On Tue, Sep 2, 2014 at 3:50 PM, Mallory van Achterberg < <EMAIL REMOVED> > wrote:
> On Tue, Sep 02, 2014 at 02:40:22PM -0500, Michael Tangen wrote:
> > It all has to do with the placement of role="menu", role="menuitem"
> > and a variety of other ARIA attributes.
>
> My fault for mentioning menus... it's apparently the entire site in
> this case.
>
> > - I also found that for some reason, the *first level* LI tags need an
> > attribute role="menu" if you want the presence of a sub-menu to be
> > announced.
> Yeah the specs mention the main ul is "menubar" while the li's are
> "menu"s.
> I would think this is to do with the type of "menu" the specs seem to
> be written for: application menus where each option is often itself a
> sort of mini-application-menu.
>
> _mallory
> > > list messages to <EMAIL REMOVED>
>
- Next message: Whitney Quesenbery: "Re: Accessible color and contrast for projected presentations"
- Previous message: Michael Tangen: "Re: Keyboard navigation using arrows only"
- Next message in Thread: Michael Tangen: "Re: Keyboard navigation using arrows only"
- Previous message in Thread: Michael Tangen: "Re: Keyboard navigation using arrows only"
- View all messages in this Thread