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

@verndale/accessibility-standards

v4.0.0

Published

Deterministic accessibility semantics, patterns, applicability, and consumer projections

Readme

Accessibility Standards

@verndale/accessibility-standards is Verndale's canonical, versioned authority for accessibility semantics, interaction patterns, applicability decisions, and evidence routing.

UI Design Brain remains the separate authority for canonical UI pattern names and aliases. This package pins its catalog manifest and projects a validated binding from canonical UI slugs to accessibility pattern and capability-filtered baseline semantic IDs. The binding classifies every catalog slug as direct, candidate, or baseline-only; aliases and free-form Markdown never enter applicability evaluation.

The package projects the same source records into two purpose-specific profiles:

  • conductor — Functional Specification and Acceptance Criteria contracts.
  • ai-orchestration — implementation, testing, and review Build Pack contracts.

Consumers pin an exact package version and commit a config, route map, and generated provenance. Generated outputs are deterministic and carry a do-not-edit marker plus source/config/route digests.

The current schema-4 projection targets @verndale/[email protected]. Schema 4 retains complete semantic traceability for all 55 WCAG 2.2 Level A/AA criteria and adds the HTML inert contract, ARIA in HTML author-conformance authority, plus an explicit inventory for all 30 entries in the WAI-ARIA APG pattern index and all seven entries in its Practices index. Missing composite widgets, cross-cutting semantic rules, and fail-closed UI discriminators are now part of the versioned contract; no current APG pattern remains deferred.

Commands

pnpm verify:ci
pnpm build
pnpm exec accessibility-standards sync --config accessibility-standards.config.json
pnpm exec accessibility-standards sync --if-needed --config accessibility-standards.config.json
pnpm exec accessibility-standards check --config accessibility-standards.config.json

See authoring, the projection contract, and versioning.