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

react-a11y-components

v0.0.5

Published

[![Build Status](https://travis-ci.org/mfrachet/react-a11y-components.svg?branch=master)](https://travis-ci.org/mfrachet/react-a11y-components) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

Downloads

12

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

skahrzskahrz

Keywords

Readme

Build Status License: MIT

Style-less and opinionated accessible components for React applications. This library is work in progress.

Why such a library?

I see plenty of UI components libraries or public design system implementations popping all over Github with their own accessibility tricks and implementations. And this is great when people have the chance to use these libraries in their project.

But often times, people implement their own UI library for their current project by hand, without tools - which is also really great.

The problem I want to solve is the following: when building a UI library for a dedicated project, I'm feeling that people tend to only think about the visual aspect of the product. They may not have knowledge about accessibility and it seems that we're lacking some primitives to make accessibility "easy" to deal with.

How this library tries to solve the problem?

By implementing WAI Aria Practices without any styles and leaving the DOM attributes access to the developer.

A Button in this library is an aria button but it can accept any of the HTML attributes that the button HTML element can accept also. Plus it doesn't have any style so you can focus on making it look the way you want without any reset.

What is the artifact?

$ yarn add react-a11y-components # in your react project