a11y-component-audit

a11y-component-audit is a skill for Claude Code, Codex from AmadeusITGroup/otter. It costs 40 tokens per session (788 once invoked), scanned A, original, BSD-3-Clause.

A review process for checking user-interface components against WCAG AA accessibility guidelines, which cover how people with disabilities can use websites and apps.

In plain words
What is it for?
Use it to inspect ARIA labels and focus behavior, check keyboard access and contrast, review forms, images, tooltips, animations, and confirm that accessibility tests and supporting evidence exist.
Why use it?
It helps find barriers such as missing labels, poor keyboard behavior, weak color contrast, unclear errors, inaccessible images, and motion that cannot be reduced.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect ARIA labels and focus behavior, check keyboard access and contrast, review forms, images, tooltips, animations, and confirm that accessibility tests and supporting evidence exist.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amadeusitgroup/otter/a11y-component-audit
Install

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.

Any agent
npx skills add AmadeusITGroup/otter --skill a11y-component-audit
Clone the repo
git clone --depth 1 https://github.com/AmadeusITGroup/otter

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for a11y-component-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/amadeusitgroup/otter/a11y-component-audit/github.svg)](https://agentmods.dev/skills/amadeusitgroup/otter/a11y-component-audit)
Your own site
<a href="https://agentmods.dev/skills/amadeusitgroup/otter/a11y-component-audit"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/a11y-component-audit/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.

agentmods 80×15 button for a11y-component-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/amadeusitgroup/otter/a11y-component-audit"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/a11y-component-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 788 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00788
Opus 5 $0.00020 $0.00394
Sonnet 5 $0.00008 $0.00158
Haiku 4.5 $0.00004 $0.00079

Measured 9d ago against content hash 6acad6f5f175, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

a11y-component-audit 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.

tools/llm/plugins/a11y/skills/a11y-component-audit/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Component Accessibility Audit

Compliance Target

WCAG 2.1 AA for existing components. WCAG 2.2 AA for newly created components. Accessibility is a release gate, not a follow-up.

<hard_rules>

  1. Apply [[a11y-aria-patterns]] for accessible names, keyboard behavior, focus outlines, and validation ARIA.
  2. Form controls: programmatic label (<label for="[id]"> or aria-labelledby). Placeholder is NOT a label.
  3. No color-only information: status, error, and category indicators carry text or icon in addition to color.
  4. Contrast: text 4.5:1 (3:1 for large text ≥18px or ≥14px bold), UI components and focus indicators 3:1. Use design tokens — no raw hex values.
  5. Reduced motion: animations longer than 200 ms must respect prefers-reduced-motion: reduce.
  6. No tooltip on disabled controls: use a visible sibling message with aria-describedby instead.
  7. Images and icons: decorative images use alt="" or aria-hidden="true"; informative images have descriptive alt text; functional images describe their purpose, not appearance; never prefix with "image of" or "icon of". </hard_rules>

Axe test coverage — verify an axe test exists for the component (follow [[a11y-axe-playwright]] for conventions). If none exists, record as a finding. Record: covered or missing — no axe test found.

Keyboard pass — follow [[a11y-keyboard-playwright]] for patterns and helpers. Record: verified or findings list.

ARIA pattern validation — validate each changed component against [[a11y-aria-patterns]]. Do NOT improvise ARIA roles. Record: named pattern(s) or finding with proposed pattern.

Contrast verification

Confirm all colors use design tokens (no raw hex). Run token contrast linter if available. Record: verified via tokens or findings list.

Reduced motion check

Confirm every animation > 200 ms has a prefers-reduced-motion: reduce rule. Record: respected or n/a — no animations.

Disabled controls (only if the component includes disabled form controls)

Read the full file on GitHub · 69 lines

Changes

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.

  1. 9d ago First seen · 69 lines · 40 tokens per session scan A 6acad6f5f175

Subscribe to this mod's changes

a11y-component-audit is a skill published in the GitHub repository AmadeusITGroup/otter (58 stars, last pushed today), licensed BSD-3-Clause. It adds 40 tokens to every session and 788 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-30.

Related

Other skills, from other repositories

igniteui-angular-figma-to-app

Translate Figma app screens designed using the Indigo.Design UI Kits into production Angular applications with Ignite UI for Angular. The Indigo.Design UI Kits are Figma component libraries available in four design-system variants — Material, Fluent, Bootstrap, and Indigo — each with light and dark themes. Designers…

IgniteUI/igniteui-angular · 210 tokens

igniteui-angular-generate-from-image-design

Implement Angular application views from design images using Ignite UI Angular components. Uses MCP servers (igniteui-cli, igniteui-theming, angular-cli) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built…

IgniteUI/igniteui-angular · 124 tokens

angular-developer

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component…

angular/angular · 77 tokens

angular-new-app

Creates a new Angular app using the Angular CLI. This skill should be used whenever a user wants to create a new Angular application and contains important guidelines for how to effectively create a modern Angular application.

angular/angular · 43 tokens

magic-ui

Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.

magicuidesign/magicui · 56 tokens

wcag22-a11y-audit

WCAG 2.2 Accessibility Audit skill that systematically evaluates web pages against 8 core Success Criteria (1.1.1, 1.4.3, 1.4.11, 2.1.1, 2.1.2, 2.4.3, 2.4.7, 4.1.2) using accessibility tree inspection and visual analysis. Use this skill when you need to perform accessibility testing/auditing on a live webpage.

AIPexStudio/AIPex · 111 tokens