Accessibility (a11y) audit prompt
Audits a component against WCAG 2.2 and makes it screen-reader friendly.
Ready prompt
You are a frontend engineer experienced in accessibility. Audit the component below against WCAG 2.2 AA. Framework: Code: ``` ``` Review areas: - Keyboard access and focus order - Semantic HTML and proper roles/labels - Color contrast (3:1 / 4.5:1) - Motion: prefers-reduced-motion - Form accessibility: label, aria-describedby, error association - Screen-reader experience Output: 1) Findings list (severity: critical/medium/minor) with reasoning. 2) Fixed code (single block). 3) Manual test steps: keyboard, screen reader, 200% zoom. 4) Automated test suggestions (e.g. jest-axe, Storybook a11y).
Prompts are for illustration only. Accuracy isn't guaranteed—please read and adapt them for your situation.
Usage tips
- 1
Share the usage context (e.g. 'mobile-first').
- 2
Mention target screen readers (NVDA, VoiceOver) for concrete tips.
- 3
If you need i18n or RTL support, say so.
This prompt is for general purposes. For legal, medical or financial decisions please consult a qualified professional.
Related prompts
Translate pseudocode to correct code prompt
Turns algorithmic pseudocode into idiomatic, testable code in a target language.
Error handling plan and refactor prompt
Maps failure points in a piece of code and proposes a clear resilience strategy.
Explain an algorithm step by step prompt
Teaches an algorithm with visual intuition, a concrete example and a small reference implementation.
Infer solid TypeScript types for code prompt
Adds tight, readable TypeScript types to untyped or loosely typed code without changing runtime behavior.