From f702f627a2afdbce0184b5bcad66be969ae8aa6e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?ArielRen=C3=A9e?= Date: Thu, 6 Aug 2020 14:11:20 -0700 Subject: [PATCH] [readme] add Spanish translation See #726. --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 5ccebc172..54cb6ab56 100644 --- a/README.md +++ b/README.md @@ -26,6 +26,12 @@ Static AST checker for accessibility rules on JSX elements. + + +#### *Read this in [other languages](https://github.com/ari-os310/eslint-plugin-jsx-a11y/blob/master/translations/Translations.md).* + +[Mexican Spanish🇲🇽](https://github.com/ari-os310/eslint-plugin-jsx-a11y/blob/master/translations/README.mx.md) + ## Why? Ryan Florence built out this awesome runtime-analysis tool called [react-a11y](https://github.com/reactjs/react-a11y). It is super useful. However, since you're probably already using linting in your project, this plugin comes for free and closer to the actual development process. Pairing this plugin with an editor lint plugin, you can bake accessibility standards into your application in real-time. @@ -80,7 +86,6 @@ Then configure the rules you want to use under the rules section. } ``` - You can also enable all the recommended or strict rules at once. Add `plugin:jsx-a11y/recommended` or `plugin:jsx-a11y/strict` in `extends`: