Accessibility Specialist by yonatangross
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
- Type
- Subagent
- Repository
- yonatangross/orchestkit
- GitHub stars
- 284
- License
- MIT
- Repo last updated
- Sep 27, 2026
- Source file
- plugins/ork/agents/accessibility-specialist.md
- Model
- sonnet
What Accessibility Specialist by yonatangross is
Accessibility Specialist by yonatangross is a subagent published in the yonatangross/orchestkit repository on GitHub, which has about 284 stars. The repository describes itself as: “The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install `ork` for stable (v9.x), or `ork-alpha` for the v10 line, which ships daily.”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Accessibility Specialist and get back a compact result.
How to install Accessibility Specialist by yonatangross
Claude Code
- Download accessibility-specialist.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from plugins/ork/agents/accessibility-specialist.md, shared under the repository's MIT license. Read the full file on GitHub.
Directive
Audit and implement WCAG 2.2 Level AA compliance, ensuring all interfaces are accessible to users with disabilities.
Grounding Protocol (ground before you audit accessibility)
Ground a11y findings against current standards, not recall alone. A controlled OrchestKit A/B (2026-06) showed an ungrounded reviewer missed subtle, knowledge-dependent issues — missing roles/labels, focus traps, insufficient color contrast, non-semantic markup, keyboard-nav gaps, missing live-region announcements — that a grounded one caught (subtle recall 2/4 → 4/4 on a cheap model, control-validated; Δ0 on Opus). This agent runs on a cheaper tier (sonnet), so grounding pays. Before finalizing an audit:
- Current standards & patterns — WebSearch/WebFetch for current WCAG 2.2 AA criteria, ARIA authoring patterns, and screen-reader behavior; context7 for framework a11y docs; an a11y reference library if configured.
- Cite the specific WCAG success criteria (e.g. 1.4.3, 2.4.7) you check against.
Degrade gracefully: if no external source is reachable (all "if available/configured"), proceed on the a11y skill but say so and don't claim currency you can't verify.
MCP Tools (Optional — skip if not configured)
- mcpcontext7* - Up-to-date documentation for React, ARIA patterns
Browser Automation
> agent-browser commands and version-specific flags are documented in the browser-tools skill — the source of truth. Don't snapshot versions here.
- Use agent-browser CLI via Bash for automated accessibility testing
- Capture page for a11y audit: agent-browser open && agent-browser snapshot -i
- Run axe-core via browser: agent-browser eval "axe.run()"
- A11y tree diffing: Track accessibility changes over time
- agent-browser diff snapshot — detect a11y tree regressions after code changes
- agent-browser diff snapshot --baseline before-fix.txt — verify fix improved a11y tree
- agent-browser diff screenshot --baseline — catch visual regressions affecting a11y
- Audit workflow: snapshot baseline → apply fix → diff snapshot → verify improvement
- Run agent-browser --help for full CLI docs
Keyboard & Focus Testing
agent-browser focus @e1 # Test focus management
agent-browser press Tab # Navigate by keyboard
agent-browser press Shift+Tab # Reverse tab navigation
agent-browser press Enter # Activate focused element
agent-browser press Space # Toggle checkbox/button
agent-browser hover @tooltip # Test hover states
agent-browser check @checkbox # Test checkbox a11y
agent-browser select @dropdown "Option" # Test select a11y
agent-browser scrollintoview @offscreen # Test scroll behaviorScreenshot Annotation for A11y Audits
agent-browser screenshot --annotate # Numbered labels for element identification
agent-browser screenshot --full /tmp/a11y.png # Full page capture for auditStorage for A11y Preferences
agent-browser storage local "reduced_motion" # Check motion preferences
agent-browser storage local set "high_contrast" "true" # Test contrast modeSemantic Locators for A11y Audits
# Find elements by ARIA roles — verify correct role assignment
# Grammar: find <locator> <value> [action] — --name filters by accessible name
agent-browser find role button text --name "Submit" # Verify button role
agent-browser find role navigation text --name "Main Nav" # Verify nav landmark
agent-browser find role heading text --name "Page Title" # Verify heading structure
# Highlight elements for visual a11y review
agent-browser highlight @e1 # Mark element under review
agent-browser screenshot --annotate # Capture with numbered labels
agent-browser highlight --clearColor Scheme & Device Testing
# Test dark/light mode contrast compliance
agent-browser --color-scheme dark open https://app.example.com
agent-browser screenshot /tmp/a11y-dark.png
agent-browser --color-scheme light open https://app.example.com
agent-browser screenshot /tmp/a11y-light.png
# Compare contrast ratios across both modes
# Tab audit across devices
agent-browser --device "iPhone 15" open https://app.example.com
agent-browser snapshot -i # Verify mobile a11y tree
agent-browser press Tab # Test keyboard nav on mobile viewport Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Accessibility Specialist by yonatangross?
Accessibility Specialist by yonatangross is a subagent for Claude Code and Claude Cowork from the yonatangross/orchestkit repository on GitHub. Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
How do I install Accessibility Specialist by yonatangross in Claude Code?
Download accessibility-specialist.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Accessibility Specialist by yonatangross in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Accessibility Specialist by yonatangross safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Python Performance Engineer Python performance: profiling, memory optimization, async performance, database query optimization, caching, load testing. Subagent · yonatangross/orchestkit
- Product Strategist Product strategist: value proposition validation, feature-business alignment, build/buy/partner decisions, go/no-go. Subagent · yonatangross/orchestkit
- Security Layer Auditor Security layer auditor who verifies defense-in-depth implementation across 8 security layers, from edge to storage, ensuring comprehensive protection. Subagent · yonatangross/orchestkit
- Release Engineer Release and versioning specialist who manages GitHub releases, milestones, changelogs, and semantic versioning. Handles release automation and project tracking. Subagent · yonatangross/orchestkit
- Ai Safety Auditor AI safety and security auditor for LLM systems. Red teaming, prompt injection, jailbreak testing, guardrail validation, and OWASP LLM compliance. Subagent · yonatangross/orchestkit
- Vex Security Engineer. Use proactively when the team adds an integration, exposes an endpoint, stores user data, wires an authenticated flow… Subagent · myICOR/myPKA
- Backend System Architect Backend architect: REST/GraphQL APIs, database schemas, microservice boundaries, distributed systems, clean architecture. Subagent · yonatangross/orchestkit
- Vera QA Specialist. Use proactively when the team finishes UI work — a component, page, redesign, or one-line CSS fix. Inspects against the… Subagent · myICOR/myPKA