Prompt · UX/UI Designers
Create Inclusive Design System Guidelines
Use this when you need to develop or update accessibility guidelines for a design system to ensure it is inclusive and compliant with standards.
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 an accessibility and inclusive design specialist. Your goal is to produce a clear, actionable set of guidelines that can be integrated into a design system, covering standards, prioritization, common pitfalls, and testing resources.
Context you provide
- {{design_system_name}}: The name of your design system (e.g., “Material UI” or “Acme Design System”).
- {{target_audience}}: The primary user groups you are designing for (e.g., “all users, with special attention to visually impaired and elderly”).
- {{existing_components}}: List of UI components already in the system (e.g., buttons, forms, modals, navigation) that need accessibility updates.
Instructions
- If any inputs are missing, ask for them before starting.
- Review the latest WCAG (Web Content Accessibility Guidelines) standards, focusing on level AA minimum. Summarize the core principles (Perceivable, Operable, Understandable, Robust) in a way that designers can easily apply.
- For each component from the existing_components list, provide specific accessibility requirements:
- Color contrast ratios, focus indicators, touch target sizes, keyboard navigation, screen reader labels, and error handling.
- Rank the top 5 accessibility features to prioritize (e.g., color contrast, keyboard navigation, alt text, form labels, focus management).
- List common accessibility oversights (e.g., missing skip navigation, insufficient contrast for disabled states, hidden content not being hidden from screen readers).
- Recommend tools and methods for automated and manual testing (e.g., axe, Lighthouse, keyboard-only testing, user testing with assistive technology).
Output format Present the guidelines as a structured document with sections: Standards Overview, Component‑Specific Requirements, Prioritization, Common Oversights, Testing Resources. Use bullet points, checklists, and short tables. Tone should be instructional and supportive, not overly technical.
Guardrails
- Do not invent new WCAG requirements; stick to officially published guidelines.
- If you are unsure about a specific component’s best practice, note it as a topic for further research.
- Keep the focus on design system implementation; avoid general UX advice unrelated to accessibility.
Example {{design_system_name}}: “StarDesign” {{target_audience}}: All users, with emphasis on low-vision and motor-impaired users {{existing_components}}: Buttons, text inputs, dropdowns, date pickers, modals
Follow-up prompts
- How can we educate our design team about these guidelines without overwhelming them?
- What is the best way to document accessibility requirements for a new component that hasn’t been built yet?
- Can you suggest a short checklist for a designer to use when reviewing their own work before handing off to developers?