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

@belenkadev/be-a11y

v1.0.0

Published

Web accesibility tools

Readme

be-a11y !

be-a11y is a Node.js-based CLI tool designed for automated evaluation and reporting of accessibility issues in HTML-based projects. It supports both local directory scanning and remote URL analysis to help developers identify common accessibility problems.

Accessibility Checker


Features

  • ✅ Detects incorrect heading level order (e.g., h1h3 skipped)
  • 🖼️ Evaluates <img> tags for appropriate alt attributes
    • ⬜ Flags empty alt attributes
    • ↔️ Detects excessively long alt texts (configurable)
    • 🌈 Verifies decorative images have empty or proper alt
    • 🔗 Highlights functional images missing descriptive alt
  • ♿ Validates aria-label and aria-labelledby usage
  • 👀 Detects elements that lack accessible names or labels (e.g., <button>, <a>, <svg>)
  • 🎨 Evaluates color contrast between text and background against WCAG 2.1 AA criteria
  • 📂 Analyzes local files in directories with supported extensions: .html, .php, .latte, .twig, .edge, .tsx, .jsx
  • 🌐 Supports remote evaluation by analyzing pages via URL
  • 📤 Optional JSON export of evaluation results
  • 🎨 CLI output is grouped, color-coded, and includes file names with line numbers
  • ▶️ Automatically excludes common build directories (e.g., node_modules, dist)
  • 📝 CI-friendly: returns a non-zero exit code when issues are found
  • 🗃️ Supports rule-based configuration via a11y.config.json
    • Enable or disable specific checks
    • Fine-tune behavior of sub-rules (e.g., alt-too-long)
  • 🔗 Checks that elements are correctly associated with form controls (via for or nesting) (new!)

Usage

Install dependencies:

npm install

Run the script:

node index.js /path/to/html/files/

# or

node index.js https://example.com

Export results to JSON (optional):

node index.js /path/to/html/files report.json

# or

node index.js https://example.com report.json

Example Configuration (a11y.config.json):

{
  "rules": {
    "heading-order": true,
    "missing-alt": true,
    "alt-empty": true,
    "alt-too-long": false,
    "alt-decorative-incorrect": true,
    "alt-functional-empty": true,
    "aria-invalid": true,
    "missing-aria": true,
    "aria-role-invalid": true,
    "missing-landmark": false,
    "contrast": true
  }
}

Configuration allows per-rule toggling. All rules are enabled by default unless explicitly disabled.


Future Tools

  • GitHub Action support
  • Rule severity levels (warning vs error)
  • CI summary report in SARIF format
  • VS Code plugin integration

🤝 Contributing

We welcome contributions from the community! Whether it's a bug fix, feature proposal, or documentation update — your input is valuable.

Please read our Contribution Guide to get started.


TL;DR: 🏩 European Accessibility Act (EAA) Compliance Support

The European Accessibility Act (EAA), effective from June 28, 2025, requires certain digital products and services to comply with accessibility standards across the EU.

While this tool does not guarantee full compliance, be-a11y supports teams in their evaluation efforts by:

  • ⚠️ Detecting common accessibility issues as outlined in standards like WCAG 2.1
  • ✅ Providing actionable findings to assist with remediation workflows
  • 🏰 Promoting awareness and adoption of inclusive development practices

More on EAA: European Commission's official page


Tool name: be-a11y Repository: https://github.com/be-lenka/be-a11y