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

I think `keyboardable` and `non-keyboardable` are good. Nearly all platforms have either hardware or onscreen keyboards. On platforms that don't have a keyboard, what would focus even mean? (I guess you could have voice focus for a voice-only device, but this seems obscure.)

`tabbable` and `non-tabbable` aren't quite accurate. The distinction is about when something is tabbable (which could depend on browser or system settings), not whether it is tabbable at all under any circumstances.

`keyboardable` is about whether the control offers more than trivial keyboard interaction once focused, not about when focus happens, so it's better in this regard.

-- 
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-591108004