speech-recognition

# Speech Recognition Accessibility Skill > **Canonical source**: `examples/SPEECH_RECOGNITION_ACCESSIBILITY_BEST_PRACTICES.md` in `mgifford/ACCESSIBILITY.md` > This skill is derived from that file. When in doubt, the example is authoritative. Apply these rules when implementing or reviewing any interface that must support speech input or voice control. **Load alongside `keyboard/SKILL.md` — speech tools often rely on keyboard and pointer emulation, so keyboard requirements are a foundation, not a substitute.** --- ## Core Mandate Speech recognition can dictate text, navigate interfaces, activate controls, emulate keyboard input, and operate a pointer. Speech recognition is not the same as speaker recognition — speech recognition interprets words and commands; speaker recognition tries to identify who is speaking. **Core principles:** 1. Use visible, persistent labels — people must be able to determine what to say without guessing a hidden name 2. Match visible labels and accessible names — if a control has visible text, its accessible name must contain that text 3. Use native semantics — correct HTML names/roles/states/values/keyboard behavior give speech tools reliable information 4. Support more than direct label activation — keyboard emulation, name/number overlays, and pointer emulation vary by product 5. Do not require fine pointer control — provide alternatives to dragging, path gestures, and precise spatial interaction 6. Accept input from more than key events — ...