WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Using has-poppup to affect touch UIs


From: Patrick H. Lauke
Date: Dec 13, 2013 6:31PM

On 14/12/2013 01:03, Steve Faulkner wrote:
> the haspopup state was not an invention of ARIA (which is the case for the
> majority of ARIA roles/states/prp[erties), aria just allows authors to set
> it whereas previously it was the domain of software implementers. As noted
> earlier in this thread, it is an MSAA state that has been available and
> used in desktop software for at least 10 years. Part of the usefulness of
> ARIA is that AT do not for the most part have to learn new semantics. The
> observed SR behavior is almost certainly derived from how the same state is
> exposed in desktop sofware

Sure, I saw that, but you yourself mentioned that under certain
conditions (regular link with aria-haspopup attribute), SRs will
actually announce "has popup" rather than "menu"...so it's not as clear
cut as saying that aria-haspopup will always simply result in the same
state/announcement being voiced, no? There must already be some kind of
differentiator (I should probably fire up aViewer and inspect that
actual values being exposed) and some logic built into the SR to
announce one or the other under certain conditions...

Patrick H. Lauke
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]

www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com | http://flickr.com/photos/redux/
twitter: @patrick_h_lauke | skype: patrick_h_lauke