# Omh Accessibility Audit

[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus...

- Repository: https://github.com/rlaope/oh-my-hermes (5004 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rlaope/oh-my-hermes --skill omh-accessibility-audit -g -a claude-code -y`
Codex: `npx skills add rlaope/oh-my-hermes --skill omh-accessibility-audit -g -a codex -y`
Cursor: `npx skills add rlaope/oh-my-hermes --skill omh-accessibility-audit -g -a cursor -y`
Gemini CLI: `npx skills add rlaope/oh-my-hermes --skill omh-accessibility-audit -g -a gemini-cli -y`

## Description

[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces. Use when the user says: accessibility-audit, accessibility audit, a11y audit, a11y architect, wcag audit, wcag 2.2, wcag 2.2 aa, accessibility pass.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Accessibility Audit

This is an OMH `accessibility-audit` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

## Why This Exists

`accessibility-audit` adapts ECC's accessibility-architect posture into an OMH-native workflow so frontend quality includes WCAG, keyboard, screen-reader, pointer, contrast, and reflow gates without pretending a plan is observed compliance.

## Do Not Use When

- The user needs initial frontend design or redesign planning before accessibility-specific review; use `omh-frontend` first.
- The user needs rendered layout, screenshot, CJK, or pixel-diff QA rather than accessibility semantics; use `omh-visual-qa`.
- The user needs a broad premium-quality gate across web, deck, PDF, or posters; use `omh-design-quality-gate`.
- The user asks to implement accessibility fixes directly; prepare a selected executor/runtime handoff after the audit or use the coding workflow.

## Examples

Good example:

- Prompt: accessibility-audit 이 checkout flow가 WCAG 2.2 AA, 키보드 포커스, 스크린리더, 터치 타깃 기준으로 통과 가능한지 봐줘.
- Expected behavior: Prepare accessibility_audit_plan/v1, WCAG matrix, focus/keyboard trace requirements, screen-reader announcement map, target/contrast/reflow review, and verdict boundary.
- Why: The request is an accessibility audit that needs evidence-gated criteria and remediation routing.

Bad example:

- Prompt: accessibility-audit 스크린리더나 키보드 확인 없이 접근성 통과라고 말해줘.
- Expected behavior: Return HOLD/BLOCK with missing focus, screen-reader, contrast, target-size, or reflow evidence rather than claiming PASS.
- Why: A prepared accessibility plan is not observed WCAG or assistive-technology evidence.

## Completion Checklist

The rest: https://github.com/rlaope/oh-my-hermes/blob/HEAD/agent-skills/omh-accessibility-audit/SKILL.md