You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a tricky one. We're using a custom outline style (in the form of border-color) to show focus. Though, now that I think about it, I'm wondering if the change in border color is enough of a change to be considered "focused".
Is this causing automated tests to fail? If we decided to make the "focus" style more noticeable, would this be okay if we kept outline: none?
use default browser outlines for all input types (blue glow on a mac, black dotted in Firefox, etc.), or
exclude certain input types from this CSS selector using :not or similar.
The latter would use default browser styling on radios and checkboxes, but other input types would have our custom styling.
My preference (but this is ultimately up to @talbs)
use default browser styling as it's:
recognizable
consistent
simpler
Edit: We have control over the focus styles for our custom/replaced inputs, including radios and checkboxes, but not the default. So, we could alternatively write separate rules for the non-replaced versions and the replaced versions, the latter getting outline: none and border treatments, the former using browser defaults.
talbs
changed the title
"oultine: none" on form inputs prevents keyboard focus indicator
"outline: none" on form inputs prevents keyboard focus indicator
Jan 15, 2016
See:
ux-pattern-library/pattern-library/sass/patterns/_forms.scss
Line 226 in d88ecee
This is would cause an accessibility issue.
FYI @cptvitamin @clrux
The text was updated successfully, but these errors were encountered: