Skip to content
React Native specific accessibility linting rules.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode Valid accessibility live region (#20) Jul 10, 2018
__tests__ remove has-accessibility-label (#82) Feb 9, 2020
docs/rules remove has-accessibility-label (#82) Feb 9, 2020
flow Feature: Custom Touchables (#31) Oct 4, 2018
src introduce platform-specific configs (#83) Feb 9, 2020
.babelrc migrate to Babel v7 (#67) Jan 4, 2020
.eslintignore 🍴 Fork eslint-plugin-jsx-a11y @ 584d21a Jul 3, 2018
.eslintrc Just use Prettier defaults (#51) Jul 19, 2019
.flowconfig 🍴 Fork eslint-plugin-jsx-a11y @ 584d21a Jul 3, 2018
.gitignore Make builds deterministic (#50) Jul 18, 2019
.npmignore 🍴 Fork eslint-plugin-jsx-a11y @ 584d21a Jul 3, 2018
.npmrc 🍴 Fork eslint-plugin-jsx-a11y @ 584d21a Jul 3, 2018
.prettierrc Just use Prettier defaults (#51) Jul 19, 2019
.travis.yml release v2.0.0-rc0 Feb 9, 2020 Task: Update docs (#16) Jul 10, 2018 introduce platform-specific configs (#83) Feb 9, 2020
package.json release v2.0.0-rc0 Feb 9, 2020
yarn.lock introduce platform-specific configs (#83) Feb 9, 2020

Maintenance Status


Eslint-plugin-react-native-a11y is a collection of React Native specific ESLint rules for identifying accessibility issues. Building upon the foundation set down by eslint-plugin-jsx-a11y, eslint-plugin-react-native-a11y detects a few of the most commonly made accessibility issues found in react native apps. These rules make it easier for your apps to be navigable by users with screen readers.



Before starting, check you already have ESLint as a devDependency of your project.

Projects created using react-native init will already have this, but for Expo depending on your template you may need to follow ESLint's installation instructions.


Next, install eslint-plugin-react-native-a11y:

npm install eslint-plugin-react-native-a11y --save-dev

# or

yarn add eslint-plugin-react-native-a11y --dev

Note: If you installed ESLint globally (using the -g flag in npm, or the global prefix in yarn) then you must also install eslint-plugin-react-native-a11y globally.


This plugin exposes four recommended configs.

Name Description
basic Only use basic validation rules common to both iOS & Android
ios Use all rules from "basic", plus iOS-specific extras
android Use all rules from "basic", plus Android-specific extras
all Use all rules from "basic", plus iOS-specific extras, plus Android-specific extras

If your project only supports a single platform, you may get the best experience using a platform-specific config. This will both avoid reporting issues which do not affect your platform and also results in slightly faster linting for larger projects.

If you are unsure which one to use, in most cases all can be safely used.

Add the config you want to use to the extends section of your ESLint config using the pattern plugin:react-native-a11y/ followed by your config name, as shown below:

// .eslintrc.js

module.exports = {
  root: true,
  extends: [

Alternatively if you do not want to use one of the pre-defined configs — or want to override the behaviour of a specific rule — you can always include a list rules and configurations in the rules section of your ESLint config.

// .eslintrc.js

module.exports = {
  root: true,
  extends: [
  rules: {
    'react-native-a11y/rule-name': 2

For more information on configuring behaviour of an individual rule, please refer to the ESLint docs

Supported Rules




Rule Options

The following options are available to customize the recommended rule set.

Custom Touchables

react-native-a11y/has-accessibility-props and react-native-a11y/no-nested-touchables allow you to define an array of names for custom components that you may have that conform to the same accessibility interfaces as Touchables.

"react-native-a11y/has-accessibility-props": [
    "touchables": ["TouchableCustom"]

Custom Invertable Components (iOS)

react-native-a11y/has-valid-accessibility-ignores-invert-colors allows you to optionally define an Array of component names to check in addition to <Image />.

For more information, see the rule docs.

"react-native-a11y/has-valid-accessibility-ignores-invert-colors": [
    "invertableComponents": [

Creating a new rule

If you are developing new rules for this project, you can use the create-rule script to scaffold the new files.

$ ./scripts/create-rule.js my-new-rule


This project started as a fork of eslint-plugin-jsx-a11y and a lot of the work was carried out by its contributors, to whom we owe a lot!


eslint-plugin-react-native-a11y is licensed under the MIT License.

Maintenance Status

Active: Formidable is actively working on this project, and we expect to continue for work for the foreseeable future. Bug reports, feature requests and pull requests are welcome.

You can’t perform that action at this time.