WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Keyboard navigation using arrows only

for

From: Michael Tangen
Date: Sep 3, 2014 10:11AM

I'm not talking about Windows menus, Bryan — just basic web-based
navigation. With a deep-linking menu on a website, both the attributes
aria-haspopup on the <a> tag and the role="menu" on the submenu UL tag cue
JAWS in on that there's a submenu and announce it accordingly. The
physical presence of an "arrow" in a website menu does not necessarily add
significant value (in my opinion) when the aforementioned attributes
facilitate the announcing of the presence of a submenu. Can it add some
level of benefit? Sure, but I think most of the value is for sited users.
Just my take on it.

Also for what it's worth, Microsoft Windows controls are irrelevant when
you're trying to build websites and be agnostic about operating systems and
browsers.




On Tue, Sep 2, 2014 at 6:52 PM, Bryan Garaventa <
<EMAIL REMOVED> > wrote:

> >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
>
>
>