accessibility-engineer

accessibility-engineer is a skill for Claude Code, Codex from mtnyilmaz/agents. It costs 58 tokens per session (2,290 once invoked), scanned A, original, MIT.

A guide for building and reviewing accessible web interfaces to WCAG 2.2 AA standards. Accessibility means making software usable with keyboards, screen readers, and other assistive technology.

In plain words
What is it for?
Use it to audit or build accessible components, forms, dialogs, keyboard navigation, semantic HTML, ARIA labels, and focus management.
Why use it?
It helps prevent barriers such as missing labels, poor contrast, broken keyboard focus, and unclear page structure.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/mtnyilmaz/agents/accessibility-engineer
Any agent
npx skills add mtnyilmaz/agents --skill accessibility-engineer
Clone the repo
git clone --depth 1 https://github.com/mtnyilmaz/agents

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 accessibility-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/mtnyilmaz/agents/accessibility-engineer.svg)](https://agentmods.dev/skills/mtnyilmaz/agents/accessibility-engineer)
Your own site
<a href="https://agentmods.dev/skills/mtnyilmaz/agents/accessibility-engineer"><img src="https://agentmods.dev/badge/skills/mtnyilmaz/agents/accessibility-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,290 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00058 $0.02290
Opus 5 $0.00029 $0.01145
Sonnet 5 $0.00012 $0.00458
Haiku 4.5 $0.00006 $0.00229

Measured 3d ago against content hash 4bf5dad87408, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

accessibility-engineer 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 3d 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.

.agents/skills/accessibility-engineer/SKILL.md · 377 lines

How it starts

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

Accessibility Engineer

Expert in building accessible UI to WCAG 2.2 AA standards. Focused on keyboard navigation, screen reader compatibility, and inclusive design.

WCAG 2.2 Target Levels

Level Requirement Examples
A Minimum Alt text, keyboard access
AA Target Contrast ratio, focus visibility
AAA Ideal Enhanced contrast, sign language

Projects target AA level.

Core Principles (POUR)

Perceivable   → Users must be able to perceive content (visual, auditory)
Operable      → Everything must be usable via keyboard
Understandable → Content and interface must be understandable
Robust        → Must be compatible with assistive technologies

Semantic HTML

✅ Correct Element Selection

// ✅ Heading hierarchy — single h1 per page
<h1>Page Title</h1>
<h2>Section</h2>
<h3>Subsection</h3>

// ✅ Meaningful landmarks
<header>...</header>
<nav aria-label="Main navigation">...</nav>
<main>...</main>
<aside aria-label="Related content">...</aside>
<footer>...</footer>

// ✅ Use ul/ol for lists
<ul>
  <li>Item 1</li>
  <li>Item 2</li>
</ul>

// ❌ Wrong — don't do everything with divs
<div class="button" onclick="...">Click</div>

// ✅ Correct — semantic button
<button type="button" onClick={...}>Click</button>

ARIA Usage

Core Rule: Semantic HTML comes first

// ✅ Native button — no ARIA needed
<button>Save</button>

// ✅ Custom component — add ARIA
<div
  role="button"
  tabIndex={0}
  aria-pressed={isActive}
  onKeyDown={(e) => e.key === 'Enter' && onClick()}
  onClick={onClick}
>
  Custom Button
</div>

Common ARIA Attributes

// Labels
<button aria-label="Search">🔍</button>
<button aria-labelledby="modal-title">Close</button>

// State
<button aria-expanded={isOpen} aria-controls="dropdown-id">
  Menu
</button>
<div id="dropdown-id" aria-hidden={!isOpen}>...</div>

// Live regions (dynamic content)
<div aria-live="polite" aria-atomic="true">
  {statusMessage}
</div>

// Required fields
<input aria-required="true" aria-invalid={!!error} />
<span role="alert">{error}</span>

// Loading state
<button aria-busy={isLoading} disabled={isLoading}>
  {isLoading ? 'Saving...' : 'Save'}
</button>

Read the full file on GitHub · 377 lines

Files

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.

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. 3d ago First seen · 377 lines · 58 tokens per session scan A 4bf5dad87408

Subscribe to this mod's changes

accessibility-engineer is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 2,290 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens