aria-labels SKILL.md skillA
aria-labels 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/aria-labels@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/aria-labels/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260529.7c05904, committed May 29, 2026
- Size
- 1,748 bytes
- Repository stars
- 74,516
- License
- MIT
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for all interactive elements. 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
# Provide accessible names for all interactive elements Interactive elements are the core of web navigation; without names, they become 'mystery meat' that users cannot confidently interact with. ## Quick Reference - Buttons, links, and other controls must have a discernable name - Names should be concise and describe the action or destination - Avoid generic names like 'Click Here' or 'More' ## Check Audit all interactive elements (buttons, links, widgets) for missing or unhelpful accessible names. ## Fix Add descriptive text content or `aria-label` attributes to all interactive elements. ## Explain Explain how clear labels on interactive elements improve accessibility and general usability. ## Code Review Review the rendered markup and interactive states that affect Provide accessible names for all interactive elements. 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/aria-labels@sha256:d7872b41649e5578The 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_jf2e5xjmqvqaxtu3)
3 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 (1748 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_jf2e5xjmqvqaxtu3 GET https://markdownregistry.com/api/v1/resolve?ref=thedaviddias/front-end-checklist/aria-labels GET https://markdownregistry.com/api/v1/blob/d7872b41649e5578ff897263985f5beb48656a8e13268582747e8e8f2352bcb5
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.