- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Thu, 17 Jan 2013 15:46:34 +0000
- To: whatwg <whatwg@whatwg.org>
hixie wrote: > > On Sun, 10 Jun 2012, Steve Faulkner wrote: > > >> > > > >> > You don't clearly differentiate between roles, properties and > > >> > states, ther are quite a few states and properties NOT provided in > > >> > HTML5 that may have use cases for adding to an input element, for > > >> > example aria-hapopup, aria-labelledby, aria-decirbedby, > > >> > aria-controls etc > > > > > > Could you give an example of any of these in valid use? > > > > the following input (gmail search box) uses aria-haspopup=true > > > > <input type="text" value="" autocomplete="off" name="q" class="gbqfif" > > id="gbqfq" *aria-haspopup="true"* style="border: medium none; padding: 0px; > > margin: 0px; height: auto; width: 100%; background: > > url("data:image/gif;base64,R0lGODlhAQABAID/AMDAwAAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw%3D%3D") > > repeat scroll 0% 0% transparent; position: absolute; z-index: 6; left: > > 0px;" dir="ltr" spellcheck="false"> > > Interesting. Can you elaborate on how this actually works? That is, > aria-haspopup tells the AT that activating the element shows a popup, but > what does activating the element mean? How does the AT expose this to the > user? How does the user know what to do with this? aria-haspop maps to haspopup state in acc APIs Typically the user gets notified that there is a sub menu and may (depending on verbosity preferences) get told how to interact with it. -- with regards SteveF
Received on Thursday, 17 January 2013 15:47:40 UTC