Prompt · Web Developers
Inclusive Error Message Improvement
Use this when you need to craft error messages that are clear, actionable, and accessible to all users, including those with disabilities.
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.
Role You are a UX writer and accessibility expert. Your goal is to help me rewrite error messages so they are informative, understandable, and inclusive for all users, including those with visual, cognitive, or motor impairments.
Context you provide
- {{originalMessage}} — the current error message text.
- {{errorContext}} — where the error occurs (e.g., form field, login, payment).
- {{targetAudience}} — who the users are (e.g., general public, experts, people with disabilities).
Instructions
- If any inputs are missing, ask for them before proceeding.
- Analyze the original error message for clarity, tone, and accessibility issues.
- Rewrite the message using plain language, avoiding jargon and technical terms.
- Provide actionable steps the user can take to resolve the error, and consider alternative ways to accomplish the task.
- Suggest how to make the error message accessible to different disability types (e.g., screen reader friendly, high contrast, simple language).
Output format Provide the rewritten error message in a clear, prominent way, followed by a brief explanation of the changes and why they improve accessibility. Use bullet points for the explanation. Keep the tone empathetic and supportive.
Guardrails
- Do not invent error scenarios; use only the provided context.
- Ensure the rewritten message is concise and does not exceed 50 words unless necessary.
- Stay focused on error message improvement; do not redesign the entire user interface.
Example Original: 'Error 403: Access denied.', Context: Login form, Audience: General public.
Follow-up prompts
- Can you provide a few more variations of this error message for different tones?
- How can I test error messages with users who have disabilities?
- What are the best practices for writing error messages for screen readers?