Re: Using aria-haspopup to simulate hover on touch-enabled devices (Windows)

I just read the article again to make certain, and it uses a menu as an 
example, but seems to imply that this can be used on any type of hover 
triggered content. It doesn't say anywhere that this should only be used on 
menus.

 Regarding NVDA and JAWS, I just tested the use of aria-haspopup on a static 
element like a Div with no roles, and it doesn't announce anything, so this 
likely wouldn't be an issue. However if the element has a role like a button 
or is an active element like a link, then it does get announced as a 
"submenu" in NVDA and as a "popup" in JAWS when no role=button is present. 
If role=button is present such as on an A tag, then JAWS announces it as a 
"menu".

----- Original Message ----- 
From: "Joseph Scheuhammer" <clown@alum.mit.edu>
To: <wai-xtech@w3.org>
Sent: Thursday, December 12, 2013 11:15 AM
Subject: Re: Using aria-haspopup to simulate hover on touch-enabled devices 
(Windows)


> On 2013-12-12 2:09 PM, Bryan Garaventa wrote:
>> One concern I have is that hover can be used for many things, not just 
>> for menus, and if devs start implementing aria-haspopup on all elements 
>> that show hover activity, screen readers like JAWS and NVDA will be 
>> announcing "Menu" and "Submenu" everywhere.
>
> Right.  The spec states that aria-haspopup is for menus:
> " Indicates that the element has a popup context menu or sub-level menu."
>
> I goes on to say that tooltips are not considered popups; tooltips 
> generally "pop up" on a mouse hover.  That entails that aria-haspopup 
> should not be used except to indicate that there is a menu associated with 
> the current element.
>
> Is Microsoft applying aria-haspopup to *any* content that can be revealed 
> on hover?
>
> -- 
> ;;;;joseph.
>
>
> 'A: After all, it isn't rocket science.'
> 'K: Right. It's merely computer science.'
>              - J. D. Klaun -
>
>

Received on Thursday, 12 December 2013 19:32:10 UTC