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/cosmix/loom/loom-accessibilitynpx skills add cosmix/loom --skill loom-accessibilitygit clone --depth 1 https://github.com/cosmix/loomWrote 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/cosmix/loom/loom-accessibility)<a href="https://agentmods.dev/skills/cosmix/loom/loom-accessibility"><img src="https://agentmods.dev/badge/skills/cosmix/loom/loom-accessibility.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.00016 | $0.04934 |
| Opus 5 | $0.00008 | $0.02467 |
| Sonnet 5 | $0.00003 | $0.00987 |
| Haiku 4.5 | $0.00002 | $0.00493 |
Grade A, and why
loom-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 yesterday.
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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility
Overview
Making web UIs usable by everyone, including keyboard-only and assistive-technology users. Covers WCAG 2.1/2.2 AA, semantic HTML, ARIA, keyboard/focus management, screen readers, contrast, and testing. Optimize for AA — that is the legal bar (ADA, EN 301 549, AODA) in most jurisdictions.
Core Rules (internalize these first)
- First rule of ARIA: don't use ARIA. A native
<button>/<a>/<input>/<nav>ships focus, keyboard, role, and state for free. ARIA only describes; it never adds behavior. Bad ARIA is worse than none. - Second rule: don't change native semantics.
<button role="heading">is a footgun. Don't override roles of interactive elements. aria-hidden="true"on a focusable element is a trap — it hides the element from the a11y tree while leaving it in the Tab order, so SR users land on "nothing." Hide the whole subtree and remove it from tab order (inert), never one or the other.- Never
outline: nonewithout a replacement. Removing the focus ring with no:focus-visiblestyle is the single most common WCAG 2.4.7 failure. - Automated tools catch ~30–40% of issues. axe/Lighthouse find contrast, missing alt/labels, dup IDs — never "is the focus order sane," "does the SR announcement make sense," "is this keyboard-operable." Manual keyboard + SR passes are mandatory.
Accessible Name Computation (the thing people get wrong)
The accessible name is what a screen reader announces. Resolution order (first non-empty wins):
aria-labelledby(space-separated IDs; concatenated text of targets) — highest priority, overrides visible contentaria-label- Native labeling:
<label for>/wrapping<label>,<img alt>,<fieldset><legend>,<figcaption>, wrapped text content of a button/link title/placeholder— fallback only; never rely on these (placeholder vanishes on input,titleis not exposed on touch/keyboard reliably)
⚠ Gotchas:
aria-labelledbyreferencing a hidden (display:none) element still contributes its text — intentional, useful for SR-only names.aria-label/aria-labelledbyare ignored on non-interactive, non-landmark elements (<div>,<span>,<p>) unless they have a role. Don't expect<span aria-label>to announce.- Icon-only controls MUST have a name:
<button aria-label="Close">✕</button>. A bare glyph/SVG announces nothing or reads the character. aria-describedbyadds supplementary description (hint, error) read after the name — it does not replace the name.
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.
- yesterday Changed · -28 tokens per session 18507fc707dd
- 4d ago First seen · 331 lines · 44 tokens per session scan A 46734c78f8bb
loom-accessibility is a skill published in the GitHub repository cosmix/loom (54 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 4,934 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-30.
Other skills, from other repositories
fixing-accessibility
Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.
accessibility
Achieve and maintain WCAG compliance through inclusive design practices, proper ARIA usage, and comprehensive testing methodologies.
winui-code-review
Code quality review for WinUI 3 apps — MVVM compliance, x:Bind correctness, accessibility, theming, security, and performance. Use before committing to catch issues that the compiler and UI tests won't find.
accessibility-fix
Scan an AEM Edge Delivery Services page for WCAG 2.1 AA accessibility violations and generate specific fixes. Identifies missing alt text, heading hierarchy issues, link text problems, color contrast concerns, and EDS-specific accessibility patterns. Use when fixing accessibility issues, preparing for compliance…
docs-check-style
Check documentation for Elastic style guide compliance using Vale linter output and style rules. Use when writing, editing, or reviewing docs to catch voice, tone, grammar, formatting, accessibility, and word choice issues.
accessibility-testing-expert
Expert guide for automated and manual Web Accessibility (a11y) testing — axe-core, Pa11y, Playwright a11y, screen reader testing, and WCAG 2.2 Level AA/AAA compliance / Panduan ahli pengujian aksesibilitas web.