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

cucumber-puppeteer-axe

v1.1.3

Published

This package contains step definitions to test webpages for accessibility issues with AxeCore

Downloads

9

Readme

Build Status

CucumberPuppeteerAxe

Step definitions to test webpages for accessibility issues with AxeCore

How to use

This setup relies on the package cucumber-puppeteer to work properly.

Checkout this setup to see how you can use this in your project.

If you're using docker then you should checkout puppeteer-cucumber. It is a pre-build docker container for testing with cucumber and puppeteer. This package is also included so you can check for accessibility issues right away!

Available steps

Select tags

Given I use the accessibility standards "wcag2a,wcag2aa"

This statement will set the tags for standards you want to use for the scenario you are running.

Select the standards you want to use. See the axe website for a list of supported tags.

Disable rules

When I disable the accessibility rule "color-contrast,link-name"

Disable accessibility rules for the current scenario

Test the whole page

Then the page should be accessible

Test a section of a page

Then the section "#content" should be accessible

Exclude something when testing the whole page

Then the page excluding "#content img" should be accessible

Exclude something when testing a section

Then the section "#homepage" excluding "img" should be accessible

Output

All output is directly visible in the command line:

Example output in the pipeline

If you can't find your elements it is quite easy to find them with the unique selector shown in the output (colored cyan) and add custom styling to them.

Show the error