Re: [w3c/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762)

I'm concerned "keyboardable" will create confusion with things like buttons, which as @othermaciej points out earlier in the thread, offer some minimal keyboard interaction as a fallback. And what about something like a [slider](https://www.w3.org/TR/wai-aria-practices-1.1/#slider), which has relatively complex keyboard interaction, but probably wouldn't be considered "keyboardable"?

I think the critical concept (other than `<select>`, which IMO is an outlier) is whether you _primarily_ interact with something via the keyboard - i.e. whether you can type into it.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/762#issuecomment-591113308