omh-accessibility-audit

# Accessibility Audit This is a Hermes-native `accessibility-audit` workflow skill. ## 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 `frontend` first. - The user needs rendered layout, screenshot, CJK, or pixel-diff QA rather than accessibility semantics; use `visual-qa`. - The user needs a broad premium-quality gate across web, deck, PDF, or posters; use `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 claim...