Hi Jake,
Is there a rendered version of that component?
From the code, I’d point to the element with tabindex=”0” as the thing the user is interacting with, but I’ve no idea how it’s rendered.
-Alastair
From: "Abma, J.D. (Jake)"
Depending on the 'button' as "user-interface component" is also not fine as we do not USE them visually (for visual purposes), can even make them 1px by 1px and so the focus indicator of 2 CSS px would be fine?
________________________________
From: Abma, J.D. (Jake) <
Hi Alastair,
I just took your example as a starting point to make a statement.
We can think of so many other ways this can take form and where the limitations of the SC right now will prevent adaption because proper indicators will fail and design solutions will not be possible anymore.
Please see code below where we use web component structures where the parent / main container, click-area and button are separated and focus indicators are made to fit OR buttons OR placement (like top right corner in dialog OR on touch target area (depending on need of design)
But before we talk too much code, having a clear focus indicator so people see where the focus is and failing that same indicator because the touch target gets bigger doesn't feel correct.
Depending on the 'button' as "user-interface component" is also not fine as we do not them visually, can even make them 1px by 1px and so the focus indicator of 2 CSS px would be fine?
[cid:image001.png@01D5AF6E.FBEEC410]
________________________________
