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

@houserules/plugin-accessibility

v0.1.3

Published

houserules plugin: WCAG routing and lookup for agents editing HTML and HTML-like markup.

Readme

@houserules/plugin-accessibility

npm

An agent editing markup gets accessibility wrong in predictable ways: a click handler on a <div>, an <img> with no alt decision, a label that is not associated with its control. This plugin does not answer that with more prose in always-loaded context. It ships a two-step lookup the agent can run: decide which success criteria the change is subject to, then read only those criteria from a local copy of WCAG 2.2.

Install

pnpm add -D @houserules/plugin-accessibility
pnpm exec houserules init

Requires @houserules/cli. init is what writes the modules into .claude/. Both modules are off by default, so select them when init asks.

Modules

  • accessibility installs .claude/rules/accessibility.md, a path-scoped rule for HTML and HTML-like markup, the 87 WCAG 2.2 success criteria as a pull-only reference at .claude/reference/wcag22.md, and wcag.mjs, which routes changed files to the criteria in play and looks any of them up. Optional per-framework guides for React, Svelte, Vue, and plain HTML or Astro install through the module's options.

    Scoped to **/*.html, **/*.jsx, **/*.tsx, **/*.svelte, **/*.vue, and **/*.astro through its paths: frontmatter. Claude Code loads it only when a matching file is in the working set. Keep that frontmatter. A rule file without paths: is loaded on every turn.

  • accessibility-review installs the /accessibility-review skill and a read-only accessibility-reviewer agent that audits a markup diff against the criteria the router names. Needs the accessibility module for the script and the reference corpus.

The loop

node .claude/scripts/wcag.mjs applies src/Button.tsx   # which criteria are in play
node .claude/scripts/wcag.mjs lookup 2.5.8             # read one of them
node .claude/scripts/wcag.mjs patterns                 # the whole routing table

applies is deliberately over-inclusive. Naming a criterion that turns out not to apply costs one read. Missing one costs a defect.

It is not a linter, on purpose

eslint-plugin-jsx-a11y, eslint-plugin-vuejs-accessibility, and Svelte's own compiler warnings already do the mechanical checking, and they are better at it than anything shipped here would be. This plugin owns the routing and the reasoning, and points at those for the rest. houserules doctor warns when a repo has a markup framework and no accessibility linter configured for it.

Nothing here decides contrast ratios, real focus order, or whether alt text is meaningful. Those need a rendered page or human judgment, and the rule, the skill, and the agent all say so rather than guessing.

The reference is pull-only

.claude/reference/wcag22.md is roughly 48KB. Grep it for a criterion number or a keyword and read that window. Never read it whole, and never @-import it. The read-guard module makes that mechanical rather than advisory.

The file is generated, not hand-written. pnpm --filter @houserules/plugin-accessibility wcag:regen rebuilds it from the W3C source at a pinned tag, and regenerating produces a byte-identical file.

Credits

payload/reference/wcag22.md is derived from Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, generated from the w3c/wcag repository at tag WCAG22-20241212.

Copyright © 2023 W3C®. This software or document includes material copied from or derived from Web Content Accessibility Guidelines (WCAG) 2.2, https://www.w3.org/TR/WCAG22/.

It is used under the W3C Document License, which permits derivative works in supporting materials accompanying software. The MIT license covering the rest of this package does not cover that file. The full notice is in this package's LICENSE.

Part of houserules

houserules is a portable set of Claude Code infrastructure that keeps the agent's context lean. This is one of twelve first-party plugins. The package list has the rest.

License

MIT. See LICENSE.