Bump packages to fix linter
This commit is contained in:
parent
ed9506bbaf
commit
0a11e3fdd9
6063 changed files with 378752 additions and 306784 deletions
30
node_modules/eslint-plugin-jsx-a11y/docs/rules/no-access-key.md
generated
vendored
Normal file
30
node_modules/eslint-plugin-jsx-a11y/docs/rules/no-access-key.md
generated
vendored
Normal file
|
|
@ -0,0 +1,30 @@
|
|||
# jsx-a11y/no-access-key
|
||||
|
||||
💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
|
||||
|
||||
<!-- end auto-generated rule header -->
|
||||
|
||||
Enforce no accessKey prop on element. Access keys are HTML attributes that allow web developers to assign keyboard shortcuts to elements. Inconsistencies between keyboard shortcuts and keyboard commands used by screenreaders and keyboard-only users create accessibility complications so to avoid complications, access keys should not be used.
|
||||
|
||||
### References
|
||||
1. [WebAIM](https://webaim.org/techniques/keyboard/accesskey#spec)
|
||||
|
||||
## Rule details
|
||||
|
||||
This rule takes no arguments.
|
||||
|
||||
### Succeed
|
||||
```jsx
|
||||
<div />
|
||||
```
|
||||
|
||||
### Fail
|
||||
```jsx
|
||||
<div accessKey="h" />
|
||||
```
|
||||
|
||||
## Accessibility guidelines
|
||||
General best practice (reference resources)
|
||||
|
||||
### Resources
|
||||
- [WebAIM, Keyboard Accessibility: Accesskey](https://webaim.org/techniques/keyboard/accesskey#spec)
|
||||
Loading…
Add table
Add a link
Reference in a new issue