Borrowing it
Nothing to install: this file belongs to DanielPodolsky/ownyourcode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DanielPodolsky/ownyourcode/main/.claude/skills/fundamentals/accessibility/SKILL.mdgit clone --depth 1 https://github.com/DanielPodolsky/ownyourcodeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/danielpodolsky/ownyourcode/accessibility)<a href="https://agentmods.dev/skills/danielpodolsky/ownyourcode/accessibility"><img src="https://agentmods.dev/badge/skills/danielpodolsky/ownyourcode/accessibility/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/danielpodolsky/ownyourcode/accessibility"><img src="https://agentmods.dev/badge/skills/danielpodolsky/ownyourcode/accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.01836 |
| Opus 5.5 | $0.00020 | $0.00734 |
| Sonnet 5.5 | $0.00010 | $0.00367 |
| Haiku 4.5 | $0.00005 | $0.00184 |
Grade A, and why
accessibility-fundamentals scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Fundamentals Review
"Accessibility is not a feature, it's a requirement. If 15% of users can't use your app, you've failed 15% of users."
When to Apply
Activate this skill when:
- Reviewing JSX with buttons, links, or forms
- Seeing custom interactive components
- Forms with inputs and labels
- Navigation menus
- Modal dialogs
- Any user interaction code
The Accessibility Checklist
Must Have (Every Interactive Element)
- Keyboard accessible — All actions work with Tab + Enter/Space
- Focus visible — Clear visual indicator of focused element
- Semantic elements —
<button>not<div onClick> - Form labels — Every input has an associated
<label> - Alt text — Images have descriptive alt attributes
- Sufficient contrast — Text readable against background (4.5:1 ratio)
Should Have (Complex Interactions)
- ARIA labels — Icon-only buttons have
aria-label - Focus trapping — Modals trap focus until closed
- Skip links — "Skip to main content" for keyboard users
- Live regions — Dynamic content announced to screen readers
- Error messages — Linked to inputs with
aria-describedby
Never Do
- Rely on color alone — Color should not be the only indicator
- Remove focus outlines — Never
outline: nonewithout replacement - Use divs for buttons — Use semantic
<button>or<a> - Trap users — Always provide escape from modals/menus
Common Mistakes (Anti-Patterns)
1. Div as Button
// ❌ BAD: Not keyboard accessible, no semantics
<div onClick={handleClick} className="button">
Click me
</div>
// ✅ GOOD: Native button element
<button onClick={handleClick} className="button">
Click me
</button>
Why it matters: <div onClick> doesn't receive keyboard focus, doesn't respond to Enter/Space, and isn't announced as a button by screen readers.
2. Missing Form Labels
// ❌ BAD: Input has no label
<input type="email" placeholder="Email" />
// ✅ GOOD: Label linked to input
<label htmlFor="email">Email</label>
<input id="email" type="email" placeholder="[email protected]" />
// ✅ ALSO GOOD: Wrapping label
<label>
Email
<input type="email" />
</label>
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 287 lines · 49 tokens per session scan A 9ca5a8973e62
accessibility-fundamentals is a skill published in the GitHub repository DanielPodolsky/ownyourcode (292 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 1,836 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
moai-domain-design-dna
Reverse-engineer a reference design — a screenshot, an image set, or a live URL — into a portable Design DNA JSON across three dimensions (measurable tokens, qualitative style, special-rendering effects), then generate a new self-contained artifact from that JSON. Carries the extraction rules (dominance-based colour…
moai-domain-frontend
Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.