Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add flitzrrr/frontend-design-skills --skill accessibilitygit clone --depth 1 https://github.com/flitzrrr/frontend-design-skillsWrote 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/flitzrrr/frontend-design-skills/accessibility)<a href="https://agentmods.dev/skills/flitzrrr/frontend-design-skills/accessibility"><img src="https://agentmods.dev/badge/skills/flitzrrr/frontend-design-skills/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/flitzrrr/frontend-design-skills/accessibility"><img src="https://agentmods.dev/badge/skills/flitzrrr/frontend-design-skills/accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00046 | $0.01912 |
| Opus 5 | $0.00023 | $0.00956 |
| Sonnet 5 | $0.00009 | $0.00382 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
accessibility 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 9d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility
Accessible web interfaces are mandatory -- legally, ethically, and commercially.
Scope
Use this skill when: You are auditing HTML structure and semantics, setting ARIA attributes, implementing keyboard navigation, checking contrasts, designing accessible forms, making media accessible, ensuring BFSG compliance, or auditing existing interfaces for accessibility.
Principles
1. Accessibility Is a Baseline Requirement -- Not a Special Feature
Accessible design benefits EVERYONE. Situational limitations (sunlight, noisy environments, one hand occupied) affect everyone.
2. From the Start -- Not Retrofitted
Retrofitting is 10x more expensive and 10x worse. Accessibility belongs in every phase: concept, design, development, testing.
3. The Four POUR Principles Are Mandatory
Perceivable, Operable, Understandable, Robust.
4. Technology and Design Must Work Together
Not just a developer concern (HTML) and not just a design concern (contrast). Both disciplines in sync.
5. Legal Obligation (BFSG Effective June 28, 2025)
The German Accessibility Reinforcement Act (BFSG) requires many companies to provide digital accessibility. It is not optional.
Rules
Semantic HTML
- DO: Use native elements for their purpose:
<button>for actions,<a>for navigation,<nav>,<main>,<article>. - DO: Maintain a logical heading hierarchy: exactly one
<h1>per page. Do not skip levels. - DO: Use landmark elements:
<header>,<nav>,<main>,<aside>,<footer>. - DON'T: Use
<div>or<span>for interactive elements.<div onclick>is NOT a button. - DON'T: Misuse headings for styling.
ARIA Attributes
- DO: Use ARIA only when no native HTML element fulfills the purpose.
- DO: Add
aria-labelto interactive elements without visible text (icon buttons). - DO: Use
aria-live="polite"for dynamic content (toast notifications). - DO: Use
role="alert"for error messages. - DON'T: Overload elements with ARIA. Redundant ARIA does harm.
- DON'T: Set
aria-hidden="true"on visible, interactive elements.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 187 lines · 46 tokens per session scan A 01b827d87a1f
accessibility is a skill published in the GitHub repository flitzrrr/frontend-design-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 1,912 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…