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

@democratize-quality/a11y-guard

v1.0.1

Published

AI-Powered Accessibility Regression Guardian - Catch WCAG violations early with GitHub Copilot

Readme

Democratize-Quality A11yGuard 🛡️

AI-Powered Accessibility Guardian for Modern Development by Democratize-Quality

"Shift accessibility left - catch issues during development, not after deployment."


📖 The Story

Picture this: It's Friday afternoon. Your team just shipped a beautiful new feature. The design is pixel-perfect, the animations are smooth, and everyone's celebrating. Then Monday morning arrives with a support ticket: "I can't use your app with my screen reader." Your heart sinks. Accessibility wasn't an afterthought - you even ran Lighthouse and axe-core during QA. But those tools only caught what was already built. The damage was done.

This is the accessibility gap that A11yGuard was built to close.

The Problem with Current Tools

We have amazing tools like Lighthouse, axe-core, and WAVE - they're excellent at finding accessibility issues. But they all share the same limitation: they test after you build. By the time you run them:

  • ✨ Your feature is "complete"
  • 🎨 Design decisions are finalized
  • 🏗️ Code is written and reviewed
  • 😰 Fixing issues means rework, delays, and context-switching

It's like having a spell-checker that only runs after you've published your book.

The A11yGuard Difference

A11yGuard shifts accessibility left - all the way to your development workflow:

🔍 During Development

  • Real-time scanning as you code
  • AI-powered fix suggestions in your editor
  • Interactive fixes before you even commit

🤖 Learn from Your Team

  • Builds knowledge from past violations and fixes
  • Learns patterns from git history automatically
  • Shares expertise across the team through incremental KB sync

🛡️ Proactive Prevention

  • Pre-commit hooks block regressions
  • Post-merge hooks auto-sync team knowledge
  • AI predicts risky changes before they happen

💡 Context-Aware Guidance

  • Multi-agent AI system with specialized expertise
  • Explains WCAG standards in plain language
  • Suggests fixes based on your codebase patterns

🚀 Quick Start

Prerequisites

Before you begin, ensure you have:

  1. GitHub Copilot CLI installed and authenticated

    # Install Copilot CLI
    # Visit: https://docs.github.com/en/copilot/how-tos/set-up/install-copilot-cli
       
    # Verify installation
    copilot --version
  2. Node.js 18+ installed

    node --version  # Should be 18.0.0 or higher
  3. A GitHub Copilot subscription

Installation

# Install globally via npm
npm install -g a11y-guard

# Or install in your project
npm install --save-dev a11y-guard

Initialize in Your Project

# Initialize A11yGuard (creates DB, config, git hooks)
a11y-guard init

# You'll see:
# ✅ Database: ./.a11y-guard/knowledge-base.db
# ✅ Git hooks: pre-commit, pre-push, post-merge  
# ✅ Config: .a11yguard.config.json

Your First Check

# Smart scan (default) - AI-predicted scanning
a11y-guard check

# Check with baseline comparison
a11y-guard check --compare-baseline

# Fast static analysis only
a11y-guard check --mode=static

🎯 Core Features

1. 🔍 Multi-Mode Scanning

Choose the right scanning mode for your workflow:

  • Smart Mode (default): AI predicts which files need scanning
  • Static Mode: Fast ESLint-based analysis
  • Live Mode: Real browser testing with accessibility tree inspection

Learn more about scanning modes →

2. 🤖 AI-Powered Fix Recommendations

Get intelligent, context-aware fixes powered by multi-agent AI:

# Interactive mode (default) - review and apply fixes one-by-one
a11y-guard fix src/components/Button.tsx

# Non-interactive - just show suggestions
a11y-guard fix src/components/Button.tsx --no-interactive

Six Specialized AI Agents Work Together:

  • 🔎 Scanner Agent: Detects accessibility violations
  • 📊 History Agent: Analyzes patterns from past fixes
  • 🔧 Fix Agent: Generates contextual solutions
  • 🎓 Educator Agent: Explains WCAG standards
  • ⚠️ Risk Agent: Predicts regression likelihood
  • 🐙 GitHub Agent: Integrates with repository operations

Learn more about the fix command →

3. 🧠 Team Knowledge Base

A11yGuard learns from your team's accessibility fixes automatically:

# Learn from git history
a11y-guard learn

# Full re-learn (ignore last sync)
a11y-guard learn --full --commits 200

# Incremental learning (only new commits - default)
a11y-guard learn --incremental

How Team Learning Works:

  1. Developer fixes accessibility issue → commits code
  2. Teammate runs git pull → post-merge hook triggers
  3. A11yGuard learns from diff automatically (silent)
  4. Knowledge base syncs across the team
  5. AI suggests better fixes based on team patterns

No CI/CD infrastructure needed! Just git + hooks.

Learn more about the learn command →

4. 💬 Ask Anything About Accessibility

Get instant answers about accessibility patterns:

# Ask about specific issues
a11y-guard ask "What are common button accessibility issues?"

# Get WCAG guidance
a11y-guard ask "Explain ARIA roles for navigation"

# Learn from your codebase
a11y-guard ask "What accessibility patterns does our team use?"

The AI has full context of:

  • Your knowledge base (past fixes and violations)
  • WCAG 2.1 AA standards
  • Your project structure and patterns

Learn more about the ask command →

5. 📊 Historical Analysis

Understand accessibility trends in your codebase:

# Analyze patterns
a11y-guard analyze

# Analyze specific files
a11y-guard analyze src/components/*.tsx

# See what violations are most common
# See which fixes work best for your team
# Identify high-risk areas

Learn more about the analyze command →


🏗️ Architecture

A11yGuard uses a multi-agent orchestration architecture powered by the GitHub Copilot SDK:

┌─────────────────────────────────────────────┐
│         Orchestrator Agent                  │
│         (Coordinates all subagents)         │
└─────────────────┬───────────────────────────┘
                  │
        ┌─────────┴─────────┐
        │                   │
        ▼                   ▼
┌──────────────┐    ┌──────────────┐
│   Scanner    │    │   History    │
│   Agent      │    │   Agent      │
│              │    │              │
│ • ESLint     │    │ • Pattern    │
│ • Live scan  │    │   detection  │
│ • MCP tools  │    │ • Stats      │
└──────────────┘    └──────────────┘
        │                   │
        ▼                   ▼
┌──────────────┐    ┌──────────────┐
│     Fix      │    │   Educator   │
│    Agent     │    │    Agent     │
│              │    │              │
│ • Solution   │    │ • WCAG       │
│   generation │    │   guidance   │
│ • Context    │    │ • Best       │
│   aware      │    │   practices  │
└──────────────┘    └──────────────┘
        │                   │
        ▼                   ▼
┌──────────────┐    ┌──────────────┐
│    Risk      │    │   GitHub     │
│   Agent      │    │   Agent      │
│              │    │              │
│ • Regression │    │ • Repo ops   │
│   prediction │    │ • PR context │
│ • Priority   │    │ • Diff       │
└──────────────┘    └──────────────┘

Why Multi-Agent?

  • 🎯 Specialization: Each agent is expert in its domain
  • 🔄 Parallel Execution: Multiple analyses run simultaneously
  • 🧠 Contextual Intelligence: Agents share knowledge and context
  • 🎨 Flexible Orchestration: Adapt workflow based on the task

📚 Command Reference

| Command | Description | Example | |---------|-------------|---------| | init | Initialize A11yGuard in your project | a11y-guard init | | check | Scan for accessibility violations | a11y-guard check --mode=smart | | fix | Get AI-powered fix recommendations | a11y-guard fix src/**/*.tsx | | analyze | Analyze historical patterns | a11y-guard analyze | | ask | Ask questions about accessibility | a11y-guard ask "..." | | learn | Build knowledge from git history | a11y-guard learn |


🔗 Git Integration

A11yGuard installs three git hooks automatically:

1. Pre-Commit Hook

Blocks commits with accessibility regressions

# Runs automatically on: git commit
# Command: a11y-guard check --compare-baseline --block-on-regression
# Behavior: Blocks commit if new violations found
# Bypass: git commit --no-verify

2. Pre-Push Hook

Warns about issues before push

# Runs automatically on: git push  
# Command: a11y-guard check --compare-baseline
# Behavior: Shows warnings but doesn't block
# Use: Catch issues before PR/code review

3. Post-Merge Hook (NEW)

Auto-syncs knowledge base after pull

# Runs automatically on: git pull (after merge)
# Command: a11y-guard learn --incremental --silent
# Behavior: Learns from new commits, syncs KB silently
# Result: Team knowledge stays synchronized

Smart Hook Management:

  • Preserves existing hooks (backs them up)
  • Appends A11yGuard content instead of overwriting
  • Won't create duplicates on re-initialization
  • Cross-platform compatible (Windows, macOS, Linux)

⚙️ Configuration

A11yGuard creates .a11yguard.config.json in your project:

{
  "scanMode": "smart",
  "blockOnRegression": true,
  "knowledgeBase": {
    "autoLearn": true,
    "commitLimit": 100
  },
  "exclude": [
    "**/node_modules/**",
    "**/dist/**",
    "**/*.test.{ts,tsx,js,jsx}"
  ]
}

💾 Data Storage

Per-Repository Database

A11yGuard uses a project-specific SQLite database:

your-project/
  .a11y-guard/
    knowledge-base.db  ← All data stored here
  .a11yguard.config.json
  .gitignore  ← Automatically updated

Why per-repository?

  • ✅ Each project has isolated knowledge
  • ✅ Query results are project-specific
  • ✅ No global pollution or mixed data
  • ✅ Easy to reset (just delete .a11y-guard/)

What's stored:

  • Scan results and violations
  • Successful fix patterns
  • Commit history metadata
  • Team learning progress (last learned commit)

Git integration:

  • .a11y-guard/ is automatically added to .gitignore
  • Database is NOT committed to git
  • Each developer has their own local DB
  • KB syncs via incremental learning from git history

🎓 Documentation

Command Guides

Onboarding Guide


🤝 How A11yGuard Fits Your Workflow

Development Workflow

1. Write code
   ↓
2. Run: a11y-guard fix <file>  ← Fix issues interactively
   ↓
3. git add && git commit       ← Pre-commit hook runs
   ↓
4. git push                    ← Pre-push hook warns
   ↓
5. Teammate: git pull          ← Post-merge hook auto-learns

Team Collaboration

Developer A                     Developer B
    │                               │
    ├─ Fixes violation              │
    ├─ Commits fix                  │
    ├─ Pushes to remote             │
    │                               │
    │                           ├─ git pull
    │                           ├─ post-merge hook runs
    │                           ├─ learns from Developer A's fix
    │                           └─ KB updated automatically

🔧 Troubleshooting

Copilot CLI Not Found

# Verify Copilot CLI is installed
copilot --version

# If not found, install from:
# https://docs.github.com/en/copilot/how-tos/set-up/install-copilot-cli

# Verify authentication
copilot --status

Git Hooks Not Running

# Check if hooks are executable
ls -la .git/hooks/pre-commit

# Should show: -rwxr-xr-x (executable)

# Re-initialize if needed
a11y-guard init

Database Issues

# Reset database (WARNING: Deletes all learned patterns)
rm -rf .a11y-guard/
a11y-guard init

# Or just re-learn from git
a11y-guard learn --full --commits 200

📊 Token Usage & Costs

A11yGuard uses GitHub Copilot's API, which is included in your Copilot subscription:

  • Copilot Individual/Business/Enterprise: No additional API costs
  • Token tracking: Displayed after each command
  • Caching: Prompt caching reduces token usage significantly

Example token usage:

✅ Fix applied successfully!

📊 Token Usage:
  Input tokens:    62,288 (46,179 cached)
  Output tokens:    1,298
  Cache tokens:    46,179
  Total tokens:    63,586

🌟 Why A11yGuard?

| Feature | Lighthouse | axe-core | A11yGuard | |---------|-----------|----------|-----------| | When it runs | After build | After build | During development | | AI-powered fixes | ❌ | ❌ | | | Learns from team | ❌ | ❌ | | | Pre-commit blocking | ❌ | ❌ | | | Interactive fixes | ❌ | ❌ | | | Context-aware | ❌ | ❌ | | | Git integration | ❌ | ❌ | | | Multi-agent AI | ❌ | ❌ | |

Use A11yGuard alongside Lighthouse and axe-core:

  • A11yGuard: Development-time prevention
  • Lighthouse/axe-core: Pre-production validation

📜 License

MIT


🙏 Acknowledgments

Built with:


🚀 Get Started Now

# 1. Install
npm install -g a11y-guard

# 2. Initialize
a11y-guard init

# 3. Check your code
a11y-guard check

# 4. Fix issues interactively
a11y-guard fix src/components/Button.tsx

# 5. Ask questions
a11y-guard ask "What are common form accessibility issues?"

Make accessibility a first-class citizen in your development workflow - not an afterthought. 🛡️


Built with ❤️ for inclusive web development quality by Democratize-Quality