$npx -y skills add rlaope/oh-my-hermes --skill accessibility-audit[omh] Hermes Accessibility Audit workflow: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces.
| 1 | # Accessibility Audit |
| 2 | |
| 3 | This is a Hermes-native `accessibility-audit` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user needs initial frontend design or redesign planning before accessibility-specific review; use `frontend` first. |
| 12 | - The user needs rendered layout, screenshot, CJK, or pixel-diff QA rather than accessibility semantics; use `visual-qa`. |
| 13 | - The user needs a broad premium-quality gate across web, deck, PDF, or posters; use `design-quality-gate`. |
| 14 | - The user asks to implement accessibility fixes directly; prepare a selected executor/runtime handoff after the audit or use the coding workflow. |
| 15 | |
| 16 | ## Examples |
| 17 | |
| 18 | Good example: |
| 19 | |
| 20 | - Prompt: accessibility-audit 이 checkout flow가 WCAG 2.2 AA, 키보드 포커스, 스크린리더, 터치 타깃 기준으로 통과 가능한지 봐줘. |
| 21 | - Expected behavior: Prepare accessibility_audit_plan/v1, WCAG matrix, focus/keyboard trace requirements, screen-reader announcement map, target/contrast/reflow review, and verdict boundary. |
| 22 | - Why: The request is an accessibility audit that needs evidence-gated criteria and remediation routing. |
| 23 | |
| 24 | Bad example: |
| 25 | |
| 26 | - Prompt: accessibility-audit 스크린리더나 키보드 확인 없이 접근성 통과라고 말해줘. |
| 27 | - Expected behavior: Return HOLD/BLOCK with missing focus, screen-reader, contrast, target-size, or reflow evidence rather than claiming PASS. |
| 28 | - Why: A prepared accessibility plan is not observed WCAG or assistive-technology evidence. |
| 29 | |
| 30 | ## Completion Checklist |
| 31 | |
| 32 | - The platform, target surfaces, critical tasks, WCAG level, supplied evidence, and missing observations are explicit. |
| 33 | - The wcag_success_criteria_matrix/v1 separates PASS/HOLD/BLOCK and maps each issue to user impact. |
| 34 | - Semantic structure, focus/keyboard, screen-reader announcements, target size/pointer, contrast/reflow, and form/status behavior are separate checks. |
| 35 | - PASS is unavailable unless evidence is fresh after the latest UI edit and covers critical tasks. |
| 36 | - Remediation, frontend implementation, visual QA, browser proof, CI, release, and merge remain separate observed states. |
| 37 | |
| 38 | ## Recovery Notes |
| 39 | |
| 40 | - If no rendered or DOM/accessibility-tree evidence exists, prepare the audit plan and mark verdict BLOCKED_BY_MISSING_ACCESSIBILITY_EVIDENCE. |
| 41 | - If automated scan output exists without keyboard or screen-reader evidence, keep the verdict HOLD and request the smallest focus/announcement trace. |
| 42 | - If the request is mostly visual layout or CJK clipping, route to visual-qa while preserving accessibility follow-up checks. |
| 43 | |
| 44 | ## OMH Context Rail |
| 45 | |
| 46 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 47 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 48 | - Current lane: **Materials and visual summaries** (`design-orchestration`, `design-quality-gate`, `frontend`, `accessibility-audit`, `visual-qa`, `content-operator`, `media-input-operator`, `materials-package`, `+3 more`) - web, accessibility, visual QA, files, and packages. |
| 49 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 50 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 51 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 52 | - Coverage: Every generated workflow skill carries this rail. |
| 53 | - Normal users talk to Hermes; OMH CLI is infra. |
| 54 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 55 | |
| 56 | ## Use When |
| 57 | |
| 58 | Use when Hermes must audit a UI or design system for WCAG 2.2 AA, keyboard reachability, focus flow, screen-reader semantics, target size, contrast, reflow, and accessibility evidence before claiming pass. |
| 59 | |
| 60 | Strong routing signals: `accessibility-audit`, `accessibility audit`, `a11y audit`, `a11y architect`, `wcag audit`, `wcag 2.2`, `wcag 2.2 aa`, `accessibility pass`, `accessibility check`, `screen reader`, `screenreader`, `aria audit`, `keyboard navigation`, `focus order`, `focus appearance`, `focus trap`, `tab order`, |