- From: Rob Dodson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Jun 2017 19:07:06 +0000
- To: public-css-archive@w3.org
I don't think this needs to be seen as being only for keyboard users, quite the contrary, my hope is that `:focus-ring` could make it easier for users to define when they want to see focus indicators. Here's the relevant bit of spec language: > an E element that has user input focus, **_and the UA has determined that a focus ring or other indicator should be drawn for that element_** Since the UA gets to determine when to draw a focus ring, it means we now have access to some interesting options. For example, today the UA checks to see if the user is using a keyboard to move around, if they are, then `:focus-ring` matches. But it could _potentially_ include user configuration options as well. So one day the browser could expose a user preference for strong focus indicators. Checking that option would tell the UA that even if someone clicked on a control using the mouse, it should still match `:focus-ring`. Personally I understand the argument for always displaying a focus indicator even on mouse click, but in practice I've found that these can be tough battles to win when your designers or project managers disagree. You may end up with very compromised focus styles that are subtle so as not to offend mouse users, but are therefore less useful to any user who wants a strong focus indicator. Or as @patrickhlauke pointed out, the focus indicator might be confusing to a mouse or touch user who wasn't expecting it. `:focus-ring` (hopefully) helps address this in a way that makes everyone happy. -- GitHub Notification of comment by robdodson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/709#issuecomment-308217314 using your GitHub account
Received on Tuesday, 13 June 2017 19:07:22 UTC