# Unity Accessibility

> Use when auditing Unity Accessibility: screen readers, AccessibilityNode, AssistiveSupport (desktop Narrator/VoiceOver support from Unity 6.3+).

- Skill: `rachitkumarrastogi/unity-accessibility` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rachitkumarrastogi/unity-accessibility`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rachitkumarrastogi/unity-accessibility/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: rachitkumarrastogi (https://skillmd.com/u/rachitkumarrastogi)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rachitkumarrastogi/unity-accessibility

---

# Accessibility

## Discovery

1. `get_accessibility_stack` — module/package + API script hits
2. `list_ui_documents` — UI Toolkit screens that need accessible labels
3. `find_scripts_by_content` — `AccessibilityNode`, `AssistiveSupport`

## Checklist

- Mobile (TalkBack / VoiceOver) and desktop (Narrator / VoiceOver) paths both matter on Unity 6.3+.
- Every interactive control should expose role + label; test with screen reader on.
- Keep hierarchy order matching visual reading order for focus traversal.
- Do not rely on color alone for critical state.

## Related

- `unity-ui-toolkit-tmp`, `unity-qa-scene-coverage`