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

@feedzai/react-a11y-tools

v2.0.0

Published

<div align="center"> <h1>@feedzai/react-a11y-tools</h1>

Downloads

129

Readme

Read The Docs

Table of Contents

The Problem

We find ourselves amidst the age of design systems, where virtually every company, regardless of size, has either established one or contemplated its creation. These systems serve as invaluable resources, equipping us with the means to swiftly construct seamless and uniform user interfaces.

Yet, accessibility remains a challenging endeavor, particularly when integrating frameworks like React. Whether we rely on existing design systems or embark on crafting our own from the ground up, ensuring accessibility often emerges as an afterthought. Regrettably, some companies face constraints in resources and time, making it difficult to prioritize accessibility efforts.

The Solution

Our objective is to streamline certain aspects of the accessibility journey, focusing on key areas such as focus management, navigation, and announcements.

This library offers comprehensive accessibility features and behaviors in line with the WAI-ARIA Authoring Practices, encompassing support for screen-reader and keyboard navigation.

We refrain from imposing any specific styling methodology or design requirements. Instead, our compact package delivers essential behaviors and interactions, allowing you to concentrate on your design without constraints.

Additionally, we include a straightforward testing tool to simulate a mouse-free environment, facilitating thorough accessibility testing during development.

Installation

To integrate React A11y Tools into your React project directory, execute one of the following commands:

$ npm install @feedzai/react-a11y-tools

# or if you use Yarn

$ yarn add @feedzai/react-a11y-tools

Roadmap

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

✅ - Released 🛠 - Building

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

Issues

🐛 Bugs

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

[See Bugs][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][requests]

Tests

There are three layers of tests written for this library:

  • Unit tests: we use vitest
  • Component tests: we use cypress
  • End-to-end tests: we also use cypress

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

Run all tests

npm run test

Unit tests

npm run test:unit

Cypress component tests:

npm run test:component-open

End-to-end tests:

npm run test:e2e