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

@lucasg04/jasmine-axe

v1.1.8

Published

Fork for custom Jasmine matcher for axe for testing accessibility with an up-to-date version of axe-core

Downloads

256

Readme

jasmine-axe

NPM Version GitHub package.json prod dependency version

Fork for custom Jasmine matcher for axe for testing accessibility with an up-to-date version of axe-core

Installation:

npm install --save-dev @lucasg04/jasmine-axe

Usage:

Check that there are no violations

import { TestBed } from "@angular/core/testing";
import { axe, toHaveNoViolations } from "@lucasg04/jasmine-axe";
import TestComponent from "./TestComponent.component";

describe("TestComponent", () => {
  beforeEach(() => {
    TestBed.configureTestingModule({
      declarations: [TestComponent],
    });
    TestBed.compileComponents();
    jasmine.addMatchers(toHaveNoViolations);
  });

  it("should pass accessibility test", async () => {
    const fixture = TestBed.createComponent(TestComponent);
    expect(await axe(fixture.nativeElement)).toHaveNoViolations();
  });
});

Allow some violations (for a temporary period)

If you want to add an accessibility check on an existing project, you will probably find many accessibility issues, and you may not have time to fix them right away. Instead of skipping the test until you have time to fix the issues, you can use another matcher toHaveLessThanXViolations. You will be able to prevent new accessibility issues to appear. This matcher should be use as a temporary fix, the objective is of course to have no violations at all.

import { TestBed } from "@angular/core/testing";
import { axe, toHaveLessThanXViolations } from "@lucasg04/jasmine-axe";
import TestComponent from "./TestComponent.component";

describe("TestComponent", () => {
  beforeEach(() => {
    TestBed.configureTestingModule({
      declarations: [TestComponent],
    });
    TestBed.compileComponents();
    jasmine.addMatchers(toHaveLessThanXViolations);
  });

  it("should have less than 2 accessibility issues", async () => {
    const fixture = TestBed.createComponent(TestComponent);
    expect(await axe(fixture.nativeElement)).toHaveLessThanXViolations(2);
  });
});

Axe configuration

The axe function allows options to be set with the same options as documented in axe-core:

import { axe, toHaveNoViolations } from "@lucasg04/jasmine-axe";

describe("TestComponent", () => {
  beforeEach(() => {
    TestBed.configureTestingModule({
      declarations: [],
    });
    TestBed.compileComponents();
    jasmine.addMatchers(toHaveNoViolations);
  });

  it("should demonstrate this matcher`s usage with a custom config", async () => {
    const render = () => `
        <div>
            <img src="#"/>
        </div>
    `;
    const html = render();

    const results = await axe(html, {
      rules: {
        // for demonstration only, don't disable rules that need fixing.
        "image-alt": { enabled: false },
      },
    });
    expect(results).toHaveNoViolations();
  });
});

Setting global configuration

If you find yourself repeating the same options multiple times, you can export a version of the axe function with defaults set.

Note: You can still pass additional options to this new instance; they will be merged with the defaults.

The configuration object passed to configureAxe also accepts a globalOptions property to configure the format of the data used by axe and to add custom checks and rules. The property value is the same as the parameter passed to axe.configure.

// Global helper file (axe-helper.js)
import { configureAxe } from "@lucasg04/jasmine-axe";

const axe = configureAxe({
  rules: {
    // for demonstration only, don't disable rules that need fixing.
    "image-alt": { enabled: false },
  },
  globalOptions: {
    checks: [
      /* custom checks definitions */
    ],
  },
});

export default axe;

How does it work

We export 2 custom matchers for Jasmine.
The goal is to make it super easy for developers to add automatic accessibility checks, even if they're not really familiar with accessibility, and aXe.

The matchers are just a way to encapsulate what we're testing: use the comparison we want and add a specific error message in case the check fails.

  • toHaveNoViolations: check that there are no violations at all, and if that check fails, display the results from aXe.
  • toHaveLessThanXViolations: check that there are less than allowed violations. Always display the result from aXe.

Thanks

  • jest-axe for the original idea and all the helpers that make testing with aXe super easy.
  • axe for the incredible axe-core that makes accessibility testing easy for everyone

Contributors ✨

Thanks goes to these wonderful people (emoji key):