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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@farskid/a11y

v0.3.0

Published

Automated Accessibility tests

Downloads

2

Readme

A11y

Build Status PRs Welcome license

An experimental attempt to run accessibility insights, using different insight engines.

How to install

npm install @farskid/a11y --save-dev

or

yarn add @farskid/a11y -D

How it works

The command line runs two engines, pa11y and axe core, gathers their respenctive insights, prints the report to the stdout and stores the results in a11y-report-pa11y.json and a11y-report-axecore.json inside a directory that you can define.

Example

Running from command line:

a11y --url https://localhost:3000 --out ./reports/

API

| Command line option | Descriptopn | Example | Required | Default | | :------------------ | :------------------------------------------------------------------------------------------ | :-------------------- | :------: | :-----: | | --url | Specify the url to look into | http://localhost:3000 | Yes | - | | --out | Specify the output directoty for stored reports | ./reports/ | No | ./ | | --standard | Specify the standard to test against (Supported Standards: WCAG2A,WCAG2AA,Section508) | Section508 | No | WCAG2A |

Note: --out will create all parent directories that do not exist recursively!

Note: Standards are case sensitive!

Roadmap

  • [ ] Sync stored issue interface of engines
  • [ ] Possible integration with Cypress to inspect the issues in action
  • [ ] Visualize the stored issues in a generated HTML with reasonable styles

License

MIT

Made by Farzad YZ @farzad_yz.