- From: Alexander Surkov <surkov.alexander@gmail.com>
- Date: Fri, 27 Feb 2015 09:02:48 -0500
- To: Dominic Mazzoni <dmazzoni@google.com>
- Cc: "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Received on Friday, 27 February 2015 14:03:16 UTC
I think the issue is that certain roles are not expected by the assistive technologies to have children. So technically you can do a checkbox that way but it might be confusing for AT. On the other hand a slider role [1] doesn't allow name from subtree, however it doesn't look much different from checkbox in terms of leafability. [1] http://www.w3.org/WAI/PF/aria/roles#slider On Thu, Feb 26, 2015 at 12:30 PM, Dominic Mazzoni <dmazzoni@google.com> wrote: > What's wrong with something like this, assuming it has css to make it look > like a checkbox and js to make it behave like one? > > <div tabIndex=0 role="checkbox" aria-checked="false">I agree to the > license terms</div> > > > > On Thu, Feb 26, 2015 at 4:48 AM, Alexander Surkov < > surkov.alexander@gmail.com> wrote: > >> Hi, the spec says [1] that role="checkbox" name is computed from >> "contents". Is there an use case for ARIA checkbox name computed from >> subtree? >> >> >> Thanks. >> Alexander. >> >> >> [1] http://www.w3.org/WAI/PF/aria/roles#checkbox >> > >
Received on Friday, 27 February 2015 14:03:16 UTC