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

@jtmdias/react-a11y-tools

v1.6.1

Published

A small React component library that aims to ease the process of creating accessible design systems, web apps or websites

Downloads

19

Readme

Read The Docs


Build Status Code Coverage version downloads MIT License PRs Welcome

Table of Contents

The Problem

We are in the era of design systems. Every company - from the smallest to the largest - has one or has thought about making one. These are great, and they provide the tools for building quick, fast and consistent user interfaces.

However, accessibility is still far from an easy task, especially when using libraries like React.

Whether we developers use others' design systems or build our own from scratch, accessibility is still considered a "last-minute-addition". And, sometimes, companies don't even have the resources or time to make it a priority.

The Solution

My goal is to make some parts of the accessibility process easier. Topics like focus management, navigation and announcements are all subjects we think can provide a helping hand.

This library provides accessibility and behaviour following the WAI-ARIA Authoring Practices, including screen-reader and keyboard navigation support.

We do not force any styling methodology or design-specific details. Instead, the little package provides the behaviour and interactions so that you can focus on your design.

There's also a simple testing tool so that you can emulate a no-mouse environment.

Installation

Inside your React project directory, install the package by running either of the following:

$ npm install react-a11y-tools

# or if you use Yarn

$ yarn add react-a11y-tools

Roadmap

Here is a table of the components, custom hooks and their status.

✅ - Released 🛠 - Building

| Status | Name | | ------ | ------------------ | | ✅ | Route Announcer | | ✅ | Messages Announcer | | ✅ | Focus Manager | | ✅ | Roving Tabindex | | ✅ | Keyboard Only | | ✅ | Skip Links | | ✅ | Semantic Headings | | ✅ | useTabbable |

Issues

🐛 Bugs

Please file an issue for bugs, missing documentation, or unexpected behavior.

See Bugs

💡 Feature Requests

Please file an issue to suggest new features. Vote on feature requests by adding a 👍. This helps maintainers prioritize what to work on.

See Feature Requests

Tests

There are two layers of tests written for this library:

  • We use Cypress to do component and integration testing.

To run the whole suite of tests, make sure you've done the steps in installation, then:

Run all tests

npm run test

Cypress component tests:

# In UI mode
npm run test:component-open

# in headless mode
npm run test:component-run

Integration tests:

# 1.1 Open Documentation website
npm run documentation:start

# 1.2 Open Cypress in UI mode
npm run test:integration-open