npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

fix-outline

v0.1.1

Published

`*:focus { outline: none }` done right

Downloads

234

Readme

fix-outline

*:focus { outline: none; } done right.

By default, browsers add an outline around your shiny buttons when they are focused:

This is great for keyboard accessibility, but most users don't use keyboard for navigating. The goal of this library is to provide best visual experience for most users, while keeping good keyboard accessibility.

fix-outline disables outline until user actually uses keyboard navigation. It works out of the box with your existing CSS.

This very small library has no dependencies and supports all modern browsers, including IE8+.

Install

NPM

npm install fix-outline

Usage

Remove all existing global outline rules like these:

*:focus {
  outline: 0;
}

Then call fixOutline() once in your JS:

var fixOutline = require('fix-outline');
fixOutline();

Now outline is disabled for all focused elements until keyboard navigation is used for the first time.

Advanced usage

fixOutline() automatically adds new CSS rules to your page. You can disable this behavior by setting autoCSS option to false:

var fixOutline = require('fix-outline');
fixOutline({
    autoCss: false
});

That means you need to add some CSS yourself. For example this rule is added when autoCss is enabled:

body:not(.kb-nav-used) *:focus {
  outline: none;
}

How it works

This is shortly how fix-outline works:

  • Add new CSS rule which disables outline on elements when .kb-nav-used is not defined for body
  • Setup hook, which adds .kb-nav-used class to body when TAB key is pressed

In other words, outline for elements is enabled after user uses keyboard navigation for the first time.

Reasoning behind the implementation:

  • Enables accessibility only for the ones using it.
  • Fast. Does CSS stylesheet modifications only once and removes event listener. Other implementations keep listening for all mousedown and keydown events.

Usually developers fix this by setting a global *:focus { outline: none; } rule, but they shouldn't.

Resources and other implementations

  • http://outlinenone.com/
  • http://a11yproject.com/posts/never-remove-css-outlines/
  • https://gist.github.com/jensgro/2470777
  • https://github.com/lindsayevans/outline.js

License

MIT