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

@a11yflowdev/cli

v0.1.2

Published

CLI tool for A11yFlow — WCAG 2.2 accessibility scanner

Downloads

328

Readme

@a11yflowdev/cli

CLI tool for A11yFlow — WCAG 2.2 accessibility scanner. Run scans from the terminal, get results as tables, JSON, or plain-language explanations. Built for developers, CI/CD pipelines, and AI coding agents.

Quick Start

# No install needed
npx @a11yflowdev/cli scan https://example.com

# Or install globally
npm install -g @a11yflowdev/cli

Authentication

# Option 1: Environment variable (recommended for CI)
export A11YFLOW_API_KEY=sk_live_your_key

# Option 2: Store in config file
a11yflow auth login

# Option 3: Pass inline
a11yflow scan https://example.com --key sk_live_your_key

Get an API key free at a11yflow.dev.

Commands

Scan a page

a11yflow scan https://example.com
a11yflow scan https://example.com --format plain    # plain language explanations
a11yflow scan https://example.com --format json     # machine-readable output
a11yflow scan https://example.com --standard wcag2aaa

Output (table):

Score: 74/100  |  4 violations  |  17 passes  |  2 incomplete

VIOLATIONS

  critical  button-name        2 elements   Buttons must have discernible text
  serious   color-contrast     5 elements   Elements must have sufficient colour contrast
  serious   label              1 element    Form elements must have labels
  moderate  html-has-lang      1 element    <html> element must have a lang attribute

Output (plain):

Score: 74/100

--- CRITICAL ---

button-name (2 elements)
  What's wrong:   One or more buttons don't have a name that describes what they do.
  Who's affected: Screen reader users hear "button" with no context.
  How to fix:     Add visible text inside the button, or add an aria-label.

Crawl multiple pages

a11yflow crawl https://example.com
a11yflow crawl https://example.com --mode sitemap --max-pages 25

Browse rules

a11yflow rules                        # list all rules
a11yflow rules color-contrast         # detail for one rule
a11yflow rules --impact critical      # filter by impact

Manage schedules and webhooks

a11yflow schedules list
a11yflow schedules create https://example.com --frequency daily
a11yflow webhooks list
a11yflow webhooks create https://hooks.example.com/a11y

Scan Flags

| Flag | Default | Description | |------|---------|-------------| | --standard | wcag22aa | wcag2a, wcag2aa, wcag2aaa, wcag22aa | | --format | table | table, json, plain | | --fail-on | — | Exit 1 if violations at this impact+: minor, moderate, serious, critical | | --wait | 3000 | Wait for JS rendering (0-30000ms) | | --quiet | false | Suppress progress, print only results | | --include-html | false | Include HTML of violating elements | | --include-best-practices | false | Include non-WCAG best-practice rules | | --poll-interval | 2000 | Poll interval (ms) while waiting | | --timeout | 120000 | Max wait time (ms) |

CI/CD Integration

Exit codes: 0 = pass, 1 = violations found, 2 = error.

GitHub Actions:

- name: Accessibility scan
  env:
    A11YFLOW_API_KEY: ${{ secrets.A11YFLOW_API_KEY }}
  run: npx @a11yflowdev/cli scan $DEPLOY_URL --fail-on serious

GitLab CI:

accessibility:
  script:
    - npx @a11yflowdev/cli scan $DEPLOY_URL --fail-on serious --quiet --format json > report.json
  artifacts:
    paths:
      - report.json

Links

License

MIT