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 klovaaxel/web-a11y-agent-skills --skill web-a11y-authoringgit clone --depth 1 https://github.com/klovaaxel/web-a11y-agent-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/klovaaxel/web-a11y-agent-skills/web-a11y-authoring)<a href="https://agentmods.dev/skills/klovaaxel/web-a11y-agent-skills/web-a11y-authoring"><img src="https://agentmods.dev/badge/skills/klovaaxel/web-a11y-agent-skills/web-a11y-authoring/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/klovaaxel/web-a11y-agent-skills/web-a11y-authoring"><img src="https://agentmods.dev/badge/skills/klovaaxel/web-a11y-agent-skills/web-a11y-authoring.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.00052 | $0.00497 |
| Opus 5 | $0.00026 | $0.00249 |
| Sonnet 5 | $0.00010 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
web-a11y-authoring 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 12d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web A11y Authoring
Core Rules
For concrete markup patterns, see PATTERNS.md.
- Prefer native HTML controls before ARIA or custom widgets.
- Use links for navigation and buttons for actions.
- Ensure every interactive control has a clear accessible name.
- Keep DOM order aligned with reading and interaction order.
- Preserve visible focus and keyboard operation for every interaction.
- Use ARIA only to supplement semantics that cannot be expressed natively.
- Classify images, icons, and SVG as decorative, informative, or functional.
- Communicate unusual link behavior before activation.
Authoring Checklist
Authoring checklist
- [ ] Page has meaningful title, language, landmarks, and heading structure
- [ ] Controls expose role, name, state, and value correctly
- [ ] Interactions work with keyboard alone
- [ ] Focus is visible, logical, and intentionally managed
- [ ] Hidden content is not accidentally focusable or announced
- [ ] Native control behavior is preserved under custom styling
- [ ] Links describe destination/action, including downloads and context changes
- [ ] Images, SVG, and icons have appropriate text alternatives or are hidden correctly
- [ ] Audio/video has controls and alternatives such as captions or transcripts when needed
Common Patterns
- Toggle button: native
buttonwith synchronized state such asaria-pressed. - Disclosure: button with synchronized
aria-expandedand hidden content state. - Dialog: intentional initial focus, contained interaction while open, focus restored on close.
- Icon-only control: visible or programmatic accessible name that describes the action.
- Download/file link: link text includes action, target, file type, and size when useful.
- Functional image/SVG: accessible name describes the action or destination.
- Decorative image/SVG: removed from the accessibility tree without hiding useful text.
- Media: avoid disruptive autoplay, provide controls, and include captions/transcripts when content requires them.
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.
- 12d ago First seen · 51 lines · 52 tokens per session scan A 3fb1ea0c7f71
web-a11y-authoring is a skill published in the GitHub repository klovaaxel/web-a11y-agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 497 once invoked, about $0.0003 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
Accessibility Audit Helper
Reviews UI code and components for WCAG 2.1 accessibility violations and provides specific fixes.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
a11y-planner
Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning WCAG 2.2 requirements into an accessible implementation plan with WAI-ARIA APG patterns before code hardens bad interaction and state patterns.