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 agentmods add skills/weaaare/a11y-agents-kit/aria-patternsnpx skills add weAAAre/a11y-agents-kit --skill aria-patternsgit clone --depth 1 https://github.com/weAAAre/a11y-agents-kitWrote 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/weaaare/a11y-agents-kit/aria-patterns)<a href="https://agentmods.dev/skills/weaaare/a11y-agents-kit/aria-patterns"><img src="https://agentmods.dev/badge/skills/weaaare/a11y-agents-kit/aria-patterns.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 | $0.00236 | $0.02122 |
| Opus 5 | $0.00118 | $0.01061 |
| Sonnet 5 | $0.00047 | $0.00424 |
| Haiku 4.5 | $0.00024 | $0.00212 |
Grade A, and why
aria-patterns 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 4d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ARIA Accessible Component Patterns
This skill provides deep, practical knowledge about accessible UI component patterns based on the WAI-ARIA Authoring Practices Guide (APG).
Why this skill exists
LLMs already know the ARIA spec reasonably well. What they often get wrong is the gap between spec and reality:
role="tooltip"has 3/33 MUST support on a11ysupport.io — it's essentially deadaria-modal="true"is not supported by TalkBack, Narrator, or Orca — your modal isn't actually modalaria-autocompletehas 11/55 MUST support — screen readers mostly ignore itaria-errormessagehas ~20% MUST support — designed for form errors but AT ignores it; usearia-describedbyinsteadaria-relevantis completely broken for ANY non-default value —"additions"alone has 0/11 full support (NVDA ZERO on all browsers — stops announcing entirely);"text"alone also 0/11 (Narrator, VoiceOver iOS/macOS = none);"removals"2/11 (VoiceOver only); the default"additions text"is the ONLY value that works (11/11)aria-controlsnavigation works only in JAWS — other screen readers don't expose itrole="menu"is for application commands, not site navigation — this is the #1 ARIA misusearia-busy="true"is supposed to suppress live region updates but only JAWS supports it — every other screen reader ignores itaria-live="assertive"does NOT interrupt in JAWS — the most-used desktop screen reader queues it insteadaria-detailshas 7/11 MUST support — VoiceOver (macOS + iOS), Narrator, and TalkBack completely ignore it; usearia-describedbyas primary link to descriptionsaria-activedescendantis completely unsupported for combobox on VoiceOver macOS/Safari — it works for menus but combobox options are invisible; use DOM focus (roving tabindex) insteadaria-currenthas ZERO support on Narrator and Orca — the attribute recommended for breadcrumbs, step indicators, and nav is invisible to Windows built-in and Linux screen readers; dynamic state changes only announced by NVDA and VoiceOver iOSaria-pressed="mixed"has near-zero support — only JAWS (Chrome/Firefox) and VoiceOver macOS convey the tri-state; NVDA, Narrator, Orca, TalkBack, VoiceOver iOS all ignore itaria-sortdynamic changes are announced by only NVDA+Firefox (1/11 combos) — when a user clicks a column header to change sort direction, JAWS, Narrator, VoiceOver (all platforms), Orca, and TalkBack are all silent; Orca and TalkBack can't even read static ascending/descending valuesaria-colcount="-1"(unknown column count) is broken in ALL screen readers (0/11) — every AT ignores the spec's MUST NOT and announces its own calculated count, misleading users; VoiceOver (macOS + iOS) and TalkBack don't supportaria-colcountat allaria-flowtohas 10/44 MUST support (23%) — only JAWS supports alternate reading order navigation; NVDA, VoiceOver, TalkBack, Narrator, and Orca completely ignore it, making it useless for defining multi-column or complex layout reading pathsaria-levelabove 6 has ZERO support in JAWS (all browsers) and TalkBack — only 4/11 combos fully support heading levels >6; JAWS announces "heading" with no level number; restructure headings to stay within 1–6 or encode depth context in the accessible name
What ships with it
12 files 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.
- evals/evals.json 14 KB
- references/accordion.md 20 KB
- references/at-support-gotchas.md 37 KB
- references/checkbox.md 25 KB
- references/combobox.md 39 KB
- references/dialog.md 46 KB
- references/form-validation.md 9.0 KB
- references/live-regions.md 10 KB
- references/menu.md 40 KB
- references/switch.md 25 KB
- references/tabs.md 9.9 KB
- references/tooltip.md 30 KB
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.
- 4d ago First seen · 116 lines · 236 tokens per session scan A 4cd4f716ae70
aria-patterns is a skill published in the GitHub repository weAAAre/a11y-agents-kit (33 stars, last pushed 4mo ago), licensed MIT. It adds 236 tokens to every session and 2,122 once invoked, about $0.0012 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-30.
Other skills, from other repositories
accessibility-testing-axe
Use when testing accessibility with axe.
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
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 Audit Helper
Reviews UI code and components for WCAG 2.1 accessibility violations and provides specific fixes.