el-foundation/hatch-surf
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
df378d33ef
hatch-surf/node_modules/eslint-plugin-jsx-a11y/docs/rules/no-access-key.md
Riley Zhang df378d33ef
Some checks failed
CI / go (push) Waiting to run
Details
CI / docker (push) Waiting to run
Details
CI / lint-go (push) Waiting to run
Details
CI / lint-docs (push) Waiting to run
Details
CI / check-paperclip (push) Waiting to run
Details
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Details
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Details
Merge GitHub main into Gitea repo (allow unrelated histories) 
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>
2026-06-25 05:20:46 +02:00

896 B
Raw Blame History

jsx-a11y/no-access-key

💼 This rule is enabled in the following configs: ☑️ recommended, 🔒 strict.

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

Rule details

This rule takes no arguments.

Succeed

<div />

Fail

<div accessKey="h" />

Accessibility guidelines

General best practice (reference resources)

Resources