- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 31 Jan 2012 17:08:56 -0800
- To: Charles Pritchard <chuck@jumis.com>
- Cc: Laura Carlson <laura.lee.carlson@gmail.com>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Sam Ruby <rubys@intertwingly.net>, Paul Cotton <Paul.Cotton@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, HTML WG <public-html@w3.org>
On Tue, Jan 31, 2012 at 2:29 PM, Charles Pritchard <chuck@jumis.com> wrote: > On 1/30/12 8:47 PM, Jonas Sicking wrote: >> >> So what is the most intuitive way to add a hidden >> description/summary/label? I would think "create a >> description/summary/label and then make it hidden". >> >> I.e. you'd write markup like: >> >> <label for=myinput>Label here</label><input id=myinput> >> >> and then hide the stuff that you want to only expose to AT: >> <label hidden for=myinput>Label here</label><input id=myinput> >> >> Similarly: >> <table aria-describedby="desc">...</table> >> <div hidden id=desc>Description here</div> > > > While I disagree with this method. Why? Assuming that the explicit goal is to create content only visible to AT, which is the stated requirement from the accessibility community. / Jonas
Received on Wednesday, 1 February 2012 01:09:53 UTC