Skip to main content

Adding accessibility checks to your React app

Updated - 3/9/19 This article was initially released with a reference to a third tool for React accessibility checking: react-a11y. Since publication, that library has been deprecated. The article has been updated to reflect that change.

Whether you are working for a startup, non-profit, or Fortune 500 company, accessibility is a critical component of your product. Not only it is a legal requirement in many countries1, but creating accessible applications maximizes the number of potential users. And it often has a positive impact on all users (read about the “Curb Cut Effect”).

As React developers, we have a responsibility to avoid hiding in the virtual DOM and work to ensure that the components we craft are going to work for everyone. Fortunately for us, React has React has accessibility features built into the platform to make our jobs easier.

In this article, we’re going to look at two additional tools than can help React developers create awesome and accessible applications for all.


To demonstrate these features, I’m going to bootstrap a new project with React’s Create React App. It’s a great way to spin up a new project and works nicely with the accessibility checks we’re going to implement.

If you’re looking to add these checks to a current project, the only dependency is ESLint, which we’ll look at later in this article. Now, let’s jump in!


Create React App already has wonderfully helpful console messages, and react-axe is an out-of-the-box solution that adds accessibility checking to your console.

React-axe is developed by Deque, the makers of the fantastic accessibility tools like the Axe browser extension (which I highly recommend). Install it in the usual way:

yarn add --dev react-axe

Once installed, we’ll check for a development environment before requiring and calling react-axe’s axe function and passing certain parameters.

import React from "react";
import ReactDOM from "react-dom";
import App from "./components/App";

if (process.evn.NODE_ENV === "development") {
  const axe = require("react-axe");
  axe(React, ReactDOM, 1000);

ReactDOM.render(<App />, document.getElementById("root"));

The final parameter for axe is “a timing delay in milliseconds that will be observed between each component change and the time the analysis starts” (source). We’ll set it to 1000ms, or one second.

Now if I give an element an invalid role (e.g. role="Test"), I’m met with the following console message:

▸ critical: ARIA roles used must conform to valid values

Expanding the message provides a reference to the original document, and a file and line reference to fix the issue. The console errors are helpful without being overwhelming and provide all the information and resources you need to fix the issue.

Console warnings are great, but let’s add another tool to help catch mistakes before they make it to the browser.


Jsx-a11y is an ESLint plugin that looks over your code for some key accessibility considerations. If you don’t have ESLint added to your project yet, follow their get started guide.

If you bootstrapped your React app with create-react-app like I did, it already has ESLint and some of jsx-a11y’s accessibility checking included. For the sake of this article, we’re going to add the full set of rules, so we’ll need to install the plugin library:

yarn add --dev eslint-plugin-jsx-a11y

Then modify the ESLint configs in your package.json to match the following:

  "eslintConfig": {
    "plugins": ["jsx-a11y"],
    "extends": ["react-app", "plugin:jsx-a11y/recommended"]

Now if we make a change that reduces our app’s accessibility, like removing the alt attribute for an <img>, we’re met with the following lint warning:

    Line 10:  img elements must have an alt prop, either with meaningful text, or an empty string for decorative images  jsx-a11y/alt-text

For more customization over which rules jsx-a11y uses, refer to the official documentation.

If you are using a text editor like VS Code that features in-line linting, you can identify and fix potential accessibility issues before you even save.

With these tools in place, you’re well on your way to creating more accessible React applications!


I created a11y-react-starter, a lightly-configured create-react-app with both of the above accessibility tools baked in. Check it out for a reference or use it as a starting point for your next app.


By enabling these accessibility features, you’re adding the wisdom and knowledge of the many developers who have gone before you. With their help, and a little bit of learning, anyone can create accessible applications that work for all users.

Happy coding!


  1. Web accessibility: Web accessibility legislation on Wikipedia