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 on-deck-society/love-stack --skill accessibility-compliancegit clone --depth 1 https://github.com/on-deck-society/love-stackWrote 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/on-deck-society/love-stack/accessibility-compliance)<a href="https://agentmods.dev/skills/on-deck-society/love-stack/accessibility-compliance"><img src="https://agentmods.dev/badge/skills/on-deck-society/love-stack/accessibility-compliance.svg" alt="Measured on agentmods" 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.00029 | $0.00679 |
| Opus 5 | $0.00015 | $0.00340 |
| Sonnet 5 | $0.00006 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
accessibility-compliance 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 8d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Compliance
When activated, review the user's UI code for WCAG 2.2 AA compliance. Focus on the issues most commonly shipped to production.
The Review Checklist
-
Semantic HTML: Verify the page uses semantic landmarks (header, nav, main, footer, aside, section) instead of generic divs. Flag div-only structures, missing heading hierarchy, or headings that skip levels (h1 to h3 without h2).
-
Image alt text: Every img and picture element must have meaningful alt text, or empty alt="" for decorative images. Flag images with missing, auto-generated, or placeholder alt values like "image" or the file name.
-
Form labels: Every form input must have an associated label (via for/id, aria-label, or aria-labelledby). Flag inputs without labels, placeholder-only labels, and labels without visible text.
-
Color contrast: Body text requires 4.5:1 contrast against background, large text requires 3:1 (WCAG 2.2 AA). Flag any inline or token color combinations likely to fail.
-
Keyboard navigation: Every interactive element must be reachable by Tab and operable by Enter/Space. Flag div or span elements with click handlers and no tabIndex, role, or keyboard handler.
-
Focus indicators: Interactive elements must show a visible focus ring. Flag outline:none or focus styles removed without a replacement.
-
ARIA correctness: ARIA attributes must be valid and applied to the right element. Flag aria-hidden on focusable elements, incorrect roles, missing aria-expanded on toggles, and misuse of aria-label on decorative elements.
-
Target size (WCAG 2.2 new): Interactive targets must be at least 24x24 CSS pixels (minimum), 44x44 recommended for touch. Flag small buttons, icon-only controls, and tightly packed links.
-
Motion and animation: Respect prefers-reduced-motion for any animation longer than 5 seconds or essential to meaning. Flag auto-playing video or heavy parallax without a reduced-motion variant.
-
Screen reader hazards: Flag text injected as CSS content (invisible to most screen readers), icon-font-only labels, and dynamic content regions missing aria-live.
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.
- 8d ago First seen · 47 lines · 29 tokens per session scan A d85455a7c501
accessibility-compliance is a skill published in the GitHub repository on-deck-society/love-stack (5 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 679 once invoked, about $0.0001 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
compiler-review
Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.
add-session-recording
Add privacy-aware session recording and replay to React applications using the Temps SDK. Captures user interactions for playback while respecting privacy through input masking, element blocking, and GDPR-compliant consent flows. Use when the user wants to: (1) Add session recording to their app, (2) Implement session…
wcag
Expert WCAG (Web Content Accessibility Guidelines) advisor covering WCAG 2.0, 2.1, and 2.2 — the W3C international accessibility standards. Use this skill whenever a user asks about WCAG success criteria, conformance levels (A/AA/AAA), accessibility audits, POUR principles, accessibility statements, ARIA patterns…
accessibility-auditor
Audit web pages and components for WCAG 2.2 accessibility compliance. Use when a user asks to check accessibility, find a11y issues, audit for WCAG compliance, fix screen reader problems, check color contrast, ensure keyboard navigation works, or prepare for accessibility regulations like the European Accessibility…
wicked-garden-product-accessibility
Use when auditing code for WCAG 2.1 AA compliance — keyboard navigation, ARIA patterns, color contrast, and semantic HTML. Produces prioritized remediation with code-level fixes. NOT for running automated a11y tools (use product:a11y command) or visual design review (use product/visual-review).
accessibility-audit
Audit web pages and apps for WCAG 2.1 AA accessibility compliance. Use when fixing lighthouse issues, contrast ratios, ARIA labels, or keyboard navigation.