Accessibility Requirements Specification
Create detailed accessibility requirements for [product/feature] to meet WCAG 2.1 AA standards. Include: 1) Specific success criteria applicable to the feature with implementation guidelines, 2) User flows that require special attention, 3) Input and interaction requirements (keyboard navigation, screen reader support, etc.), 4) Visual design requirements (contrast, text size, color usage), 5) Content and language guidelines, 6) Error handling and messaging adaptations, 7) Testing methodology with tools and resources, 8) Priority levels for implementation, 9) Documentation requirements for accessibility features, and 10) Training needs for the team.
How to Use This Prompt
- Copy the prompt using the button above
- Replace placeholders in [brackets] with your specific details
- Paste into your AI assistant (ChatGPT, Claude, Gemini, etc.)
- Iterate as needed - ask follow-up questions to refine the output
Why This Prompt Works
This prompt maps directly to WCAG 2.1 AA success criteria and translates abstract guidelines into concrete, implementable requirements your engineering team can act on. By covering the full spectrum from visual design to error handling to testing methodology, it eliminates the gaps that typically appear when accessibility is treated as an afterthought. The prioritization component helps teams tackle the highest-impact items first.
When to Use This Prompt
- At the start of a new feature build when you need to bake accessibility into the spec before development begins
- When preparing for an accessibility audit or remediation effort and you need a structured checklist of gaps to address
- After receiving customer complaints about usability for assistive technology users and you need to scope the fix
Tips for Better Results
- Describe the specific UI components your feature uses (modals, dropdowns, carousels) so the AI generates targeted keyboard and screen reader guidance
- Mention your tech stack (React, Angular, native iOS) so implementation guidelines match your actual development environment
- Include any existing accessibility testing tools your team already uses (axe, Lighthouse, NVDA) to get recommendations that integrate with your workflow