Re: consider modding aria-haspopup definition in 1.1

I wanted to reply in support of modifying the aria-haspopup definition to indicate that the element may open a window, dialog, pop-over, or some other type of dynamic control rather than just a menu.

Some screen readers say "pop up button" or "has pop up button menu" or "pop up menu". I don't think that because some screen readers say "menu" that the attribute should be restricted to only menus. 

A smart screen reader could look for the -haspopup attribute to see if it is inside a menubar container or role=menuitem and then speak the "menu" string, but if it's just on a plain role=button then it could just say "pop up button" like VoiceOver does. 

I think it's a simple attribute to improve accessibility that can be used in a variety of ways and is an easy sell to developers. 

I prefer this approach to visually hidden text positioning methods.

And while certainly the title attribute can be used, I think aria-haspopup is also a viable solution. 

Thanks for considering it!

Paul J. Adam
Accessibility Evangelist 
www.deque.com