(Description) Removing CSS outlines without proper fallbacks can make it impossible to navigate your site with a keyboard.
Use of the rule :focus { outline: none; }
results in the link or control being focusable but with no visible indication of focus for keyboard users. Even worse, methods to remove it such as onfocus="blur()"
result in keyboard users being unable to interact with the link or control.
If you do not like the default focus outline that is displayed when a user clicks on an interactive element, you have 3 accessible solutions:
-
Style the outline. Webkit browsers have a more prominent outline so you could try styling it to make it less obtrusive. Consider the use of
a:focus { outline: thin dotted; }
to normalize the look of the outline across browsers. -
Style the element itself. You can remove the outline as long as you style the focused element differently (using
color
,background-color
,border
ortext-decoration: underline
for example). -
Remove outlines for mouse users only, if you truly must do so. Start without applying any
outline: none
rules. If a mouse event is detected apply those rules using JavaScript. Remove the rules again if keyboard interaction is detected. Here are 2 examples of accessible outline removal scripts:
-
outliner.js, a cross-lib implementation with event delegation, by Aireh Glazer
-
outline.js, a similar approach that uses
mousedown
instead ofmouseover
, by Lindsay EvansConsider this third solution as a last resort. Some browser/screen reader combinations fire mouse events, which could cause outlines to disappear while using this method.
In conclusion, using outline: none
without proper fallbacks makes your site significantly less accessible to any keyboard only user, not only those with reduced vision. Make sure to always give your interactive elements a visible indication of focus.
Oh, right, Mac users ehe 😀
I considered using
Webkit's more prominent outline
because to me it also sounded like I was picking on Chrome but I wasn't sure if Safari was also like that.