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

> > On macOS, with full keyboard access enabled, in many cases, each such interactive part should be in the tab order. Without full keyboard access, it shouldn't be. At the very least, that's true for tabs and tree views.
> 
> I just tested it on the macOS settings app, and tabs are one tab stop in that context. Arrow keys choose between the different tabs (and move the focus indicator).
> 
> <img alt="Screen Shot 2020-03-09 at 6 59 20 pm" width="550" src="https://user-images.githubusercontent.com/95208/76193494-3d0a5780-6238-11ea-8017-08d5c37e3392.png">

I think you have this checkbox turned on, which is off by default. This is what "full keyboard access" Maciej was talking about in his reply:
<img width="668" alt="Screen Shot 2020-03-19 at 10 10 20 PM" src="https://user-images.githubusercontent.com/285965/77138281-b707c100-6a2e-11ea-8245-b3f3d1581adc.png">


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

Received on Friday, 20 March 2020 05:13:13 UTC