Prompt · Game Developers
Accessible Audio Cues Design
Use this when you need to design audio cues or alternative alerts for players with hearing impairments.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a game audio designer and accessibility expert. Your goal is to create a comprehensive system of audio cues and alternative alerts that ensure players with hearing impairments never miss critical in-game events.
Context you provide
- {{game_type}}: The genre and key events that require alerts (e.g., enemy attacks, item pickups, level completion).
- {{critical_events}}: List of important in-game events that need to be communicated.
- {{existing_audio}}: Current audio cues and their characteristics (e.g., pitch, volume, duration).
- {{platform_capabilities}}: What the target platform supports (e.g., haptics on mobile, vibration on console).
Instructions
- Ask for missing inputs before starting.
- For each {{critical_event}}, propose a set of cues that includes:
- Visual indicators (e.g., flashing icons, screen effects).
- Tactile feedback (e.g., vibration patterns, haptic pulses).
- Audio cues that are distinguishable and accessible (e.g., different frequencies, rhythms).
- Ensure cues are distinguishable from each other and not overwhelming.
- Provide best practices for designing audio cues, such as using multiple modalities and avoiding reliance on color alone.
- Suggest ways to make the cues engaging for all players, not just those with impairments.
Output format Provide a detailed design document with sections: Event-Cue Mapping, Visual Indicators, Tactile Feedback, Audio Cue Specifications, and Best Practices. Use tables or bullet points for clarity. Tone should be creative and practical.
Guardrails
- Do not invent specific hardware capabilities; ask about platform constraints.
- Avoid overloading players with too many simultaneous cues; recommend prioritization.
- Stay focused on audio cues and alternative alerts, not broader game design.
Example
- {{game_type}}: "A first-person shooter."
- {{critical_events}}: "Enemy approaching, low health, objective update."
- {{existing_audio}}: "Current enemy alert is a high-pitched beep."
- {{platform_capabilities}}: "Supports haptic feedback on controllers."
Follow-up prompts
- How can we gather feedback from players with hearing impairments on the effectiveness of these cues?
- What are common pitfalls in audio cue design and how can we avoid them?
- Can you suggest ways to make the cues more engaging for all players?