saranskumar Goal
Make interfaces accessible enough to build and ship responsibly.
When to Use
- A user-facing UI or component is being designed or reviewed.
- Forms, dialogs, tables, navigation, or async states need accessibility checks.
- Responsive and interaction decisions affect keyboard or assistive tech use.
Instructions
- Review semantics, labels, focus order, and state announcements.
- Check keyboard interaction and visible focus behavior.
- Review color, contrast, and non-color indicators.
- Note accessibility-specific implementation requirements.
Constraints
- Do not reduce accessibility to color contrast alone.
- Keep findings implementation-specific.
- Cover dynamic states, not just static markup.
Output Format
- accessibility review
- findings
- required fixes
- optional improvements
Examples
- "Review this modal flow for accessibility."
- "What accessibility requirements should this data table meet?"