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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@commercetools-uikit/accessible-hidden

v20.4.0

Published

Component to hide content offscreen while keeping it accessible. This is also helpful for testing purposes.

Downloads

20,426

Readme

AccessibleHidden

Description

This component is used to hide content offscreen, removing it from sighted users, while keeping it still accessible to screen readers and other assistive technology. It can also be useful for testing with tools like react-testing-library and cypress, which requires querying elements through content which might not be intended to be visible on screen, such as querying for a input by its label while the label is visually hidden.

It's the logical opposite of the aria-hidden attribute.

Installation

yarn add @commercetools-uikit/accessible-hidden
npm --save install @commercetools-uikit/accessible-hidden

Additionally install the peer dependencies (if not present)

yarn add react
npm --save install react

Usage

import AccessibleHidden from '@commercetools-uikit/accessible-hidden';

/**
 * In this example, we're showing additional text specifically to be read only
 * by screen readers, to make it more contextualized and easier to understand
 * for non-sighted users (as well "translating" the numeronym which might confuse
 * automatic screen-readers).
 */
const Example = () => (
  <div>
    <h3>An Article on A11y</h3>
    <p>A summary of the article</p>
    <button>
      Read More
      <AccessibleHidden> from An Article on Accessibility</AccessibleHidden>
    </button>
  </div>
);

export default Example;

Properties

| Props | Type | Required | Default | Description | | ---------- | ----------- | :------: | ------- | ----------- | | children | ReactNode | ✅ | | |

Using the component for a11y testing

This is an example for when you would want to render an input without visually displaying a label. You still would want a label to be present so it can be used when testing with RTL as well as supporting a11y.

const rendered = render(
  <>
    <AccessibleHidden>
      <label htmlFor="maiden-name-input">Enter your Maiden Name</label>
    </AccessibleHidden>
    <input id="maiden-name-input" type="text"></input>
  </>
);

expect(rendered.getByLabelText('Enter your Maiden Name')).toBeInTheDocument();
// ✓ True

It is a common requirement to show inputs inside tables. In such a case a sighted user should be able to understand the context of the input through the column header. A label element taking space inside the cell is undesirable.

References: