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

expo-accessibility-toolbox

v0.0.1

Published

Scripts and tools for auditing universal Expo apps for cross-device accessibility.

Readme

expo-accessibility-toolbox

Scripts and tools for auditing universal Expo apps for cross-device accessibility.

Status: private incubation. APIs, findings formats, and tool names are still moving. Not yet published to npm.

What this is

A TypeScript toolbox of accessibility auditors for universal Expo applications. Each auditor is the same shape: capture a surface, apply rules, emit findings. They differ only in what they capture:

  • a live DOM (axe-core over Playwright),
  • a Storybook build, story by story,
  • a native accessibility tree (Android via Maestro hierarchy, iOS via the AXe simulator CLI),
  • application source (TypeScript AST rules for React Native accessibility props),
  • theme tokens (contrast math, with color-name suggestions via chromonym).

Every auditor emits one shared findings contract: rule, pinned standard (a WCAG success criterion or platform guidance, never conflated), severity, a driveable element handle, evidence, and a machine-actionable suggested fix. Reports carry coverage accounting, so "zero findings" always distinguishes "inspected and clean" from "never inspected."

The assumption set

The word "expo" in the name is load-bearing. These tools assume a universal Expo app: React and React Native are present, Expo Router facts (such as /_sitemap route discovery and deep-link schemes) are fair game, and surfaces can be driven for real, in browsers via Playwright and on emulators/simulators via their harnesses.

Tools

| Kit | Surface | Status | |---|---|---| | axe-storybook | Built Storybook, per story (axe-core) | In development | | Web route sweep | Live DOM per route | Planned | | Android tree audit | Native tree via Maestro | Planned | | iOS tree audit | Simulator tree via AXe | Planned | | Source audit | RN accessibility props via AST | Planned | | Token contrast audit | Theme tokens | Planned |

Run every available kit with expo-a11y audit <target>, one with expo-a11y audit <target> --kits axe-storybook, and list them with expo-a11y kits. Kits that disagree about what a target is take per-kit targets and options from --config.

The Storybook kit is a maintained successor to the archived axe-storybook-testing (Chan Zuckerberg Initiative, MIT, archived January 2026); see NOTICE.md for attribution.

Development

Bun-first, matching its sibling repos (chromonym, unitforge):

bun install
bunx playwright install chromium   # once; the fixture proof drives a real browser
bun run check   # build, lint, typecheck, package surface, test

License

MIT