- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 07 May 2015 23:39:03 +0100
- To: public-webapps@w3.org
On 07/05/2015 08:59, Domenic Denicola wrote: ... > These are my thoughts as well. The proposal seems nice as a > convenient way to get a given bundle of behaviors. But we *really* > need to stop considering these "roles" as atomic, and instead break > them down into what they really mean. > > In other words, I want to explain the "button" behavior as something > like: > > - Default-focusable - Activatable with certain key commands - > Announced by AT as a button > > and then I want to be able to apply any of these abilities (or others > like them) to any given custom element. Once we have these > lower-level primitives we'll be in a much better place. Isn't that, in a way, what we currently have already? - default focusable: add tabindex=0 - activatable with certain key commands: define key command handlers yourself in JS - announced by AT as a button: role="button" P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 7 May 2015 22:39:27 UTC