accesskeys SKILL.md skillA
accesskeys from thedaviddias/front-end-checklist is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add thedaviddias/front-end-checklist/accesskeys@git:20260529.7c05904Pins git:20260529.7c05904 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- thedaviddias/front-end-checklist
- Path
skills/accesskeys/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260529.7c05904, committed May 29, 2026
- Size
- 1,750 bytes
- Repository stars
- 74,516
- License
- MIT
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure accesskey values are unique. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Ensure accesskey values are unique Duplicate access keys cause conflicts where only one element (usually the first) is reachable via the shortcut, making other elements inaccessible to keyboard users. ## Quick Reference - Each `accesskey` attribute value must be unique on the page - Duplicate access keys can lead to unpredictable browser behavior - Helps keyboard users navigate reliably using defined shortcuts ## Check Check for duplicate `accesskey` attributes across the document to ensure each shortcut is unique. ## Fix Assign unique values to each `accesskey` attribute or remove redundant ones to prevent shortcut conflicts. ## Explain Explain how duplicate access keys affect keyboard accessibility and browser shortcut handling. ## Code Review Review the rendered markup and interactive states that affect Ensure accesskey values are unique. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech. --- For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`. …
Read the whole file at its exact version.
How to install
mdr add thedaviddias/front-end-checklist/accesskeys@sha256:8996e576dd093cd1The line at the top of this page pins the label git:20260529.7c05904, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ycmylpjadxgtyjfl)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 29, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1750 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
thedaviddias/front-end-checklist · 74,516 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ycmylpjadxgtyjfl GET https://markdownregistry.com/api/v1/resolve?ref=thedaviddias/front-end-checklist/accesskeys GET https://markdownregistry.com/api/v1/blob/8996e576dd093cd1ba56593cdf65ef483b9cdc7b1afd301b2354f60721677460
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.