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

accessible-cli

v1.0.5

Published

Welcome to an attempt to make the web more inclusive. Accessible is a CLI aiming to make the web more accessible and performant. The goal: Use prominent accessibility and performance standards tooling in builds, failing when the set goals are not met. Let

Downloads

3

Readme

Accessible: The Accessibility CLI

Welcome to an attempt to make the web more inclusive. Accessible is a CLI aiming to make the web more accessible and performant. The goal: Use prominent accessibility and performance standards tooling in builds, failing when the set goals are not met. Let's see how we do this!

Table of Contents

The CLI

Accessible has two commands right out of the box: accessible create and accessible test.

Create

Accessible requires a configuration file (accessibility-config.json) and environment file to run tests. We've attempted to make this process as painless as possible with the command accessible create. There are three options with this command:

  • --env: This creates the environment file. This file is necessary for Webaim-wave and access to Webhint's Image Optimization feature. The .env file has four values:

    • API_KEY: This is your Webaim WAVE API key
    • CLOUDINARY_API_KEY
    • CLOUDINARY_API_SECRET
    • CLOUDINARY_CLOUD_NAME
  • --config: Flag used to create the configuration file accessibility-config.json at the root of the project. This file must be at the root of the project. Listed below are the seven properties available and the expected value type:

    • url [STRING]: The URL you want to test

    • tools [ARRAY]: An array of tests utilities to use. The following options are:

      • lighthouse: Google Lighthouse
      • wave: WebAim Wave
      • webhint: Microsoft Webhint

      Example configuration: tools: ["lighthouse", "wave"]

    • envPath [STRING]: The location of the .env file used for Cloudinary and Wave API keys

    • outputFolder [STRING]: The location storing the audit output file. The plugin recognizes relative paths ./ and absolute paths C:\.

    • lighthouse [OBJECT]: An object of Lighthouse tests and the user-determined passable values.

    • wave [OBJECT]: An object of WAVE tests and the user-determined passable values.

    • webhint [OBJECT]: An object of Webhint tests and the user-determined passable values.

    To exclude any irrelevant tests, delete them from the object.

  • --all: This flag creates the .env and accessibility-config.json file.

Test

Accessible's accessible test runs user-designated tests and outputs a JSON file of all failed test. The CLI reads the accessibility-config.json file, compares the tooling outputs, and creates a report of the differences.

Output

The CLI outputs a file accessibility.json with all errors based on the user-dictated tooling to user-specified path outputFolder in accessibility-config.json.

People Improving the Web

This is a list of people and companies using the CLI

If you use this CLI, please create an issue to this repo with your website. We'd love to celebrate those working to better the web.