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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@browserstack/accessibility-devtools-cli

v0.0.8

Published

Command-line interface for BrowserStack Accessibility Linter

Readme

Accessibility DevTools CLI

A command line interface to run accessibility checks on your React and HTML files.

Usage

Step 1: Installation

First, install the BrowserStack Accessibility DevTools CLI via npm

npm install -g accessibility-devtools-cli

Step 2: Authentication

  1. Sign up on http://browserstack.com
  2. Get your Username and Access Key by logging in to http://browserstack.com and going to Profile → Account & Profile → My Profile → Authentication & Security
  3. Set up the two environment variables BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY a. For Zsh, add in ~/.zshrc b. For Bash, add in ~/.bashrc or ~/.bash_profile c. For Fish Shell, add in ~/.config/fish/config.fish

Step 3: Run your tests

Run the CLI on your file(s) or directory

npx accessibility-devtools-cli --include src/**.jsx

CLI Options

--version: Show version number
--include or -i: Glob pattern(s) for files to lint
--exclude or -e: Glob pattern(s) for files to exclude from linting
--browserstack-username or -u: BrowserStack username (if not provided, taken from BROWSERSTACK_USERNAME env variable)
--browserstack-access-key or -k: BrowserStack access key (if not provided, taken from BROWSERSTACK_ACCESS_KEY env variable)
-non-strict or -n: Run in non-strict mode (only print violations, do not exit with non-success code)
--help: Show help

Exit Codes:

0 - no issues 1 - open accessibility issues 2 - BrowserStack connection issues

Sample pre-commit script:

#!/usr/bin/env bash
# Identify project root
GIT_ROOT=$(git rev-parse --show-toplevel)

# Allow skipping a11y checks
if [ -n "$SKIP_A11Y_CHECKS" ]; then
    echo "Skipping accessibility checks."
    exit 0
fi
echo "Running accessibility checks..."
if [ -n "$NON_STRICT_A11Y_CHECKS" ]; then
    # Run checks, but be lenient
    npx accessibility-devtools-cli --include $GIT_ROOT/src/**.jsx --non-strict
    exit 0
fi

# Run checks and don't let commit pass if exit code is !0
npx accessibility-devtools-cli --include $GIT_ROOT/src/**.jsx
exit $?