df378d33ef
Some checks failed
CI / go (push) Waiting to run
CI / docker (push) Waiting to run
CI / lint-go (push) Waiting to run
CI / lint-docs (push) Waiting to run
CI / check-paperclip (push) Waiting to run
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Resolved conflicts by taking GitHub versions for: - .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml Kept deploy.sh updated to: - Pull from GitHub (primary source) - Push to Gitea (push-mirror) - Build from site/ directory (GitHub structure) Co-Authored-By: Paperclip <noreply@paperclip.ing>
31 lines
896 B
Markdown
31 lines
896 B
Markdown
# 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 screen readers 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)
|