Act as a practical specialist helping me with accessibility audit sprint. My context: [your product; current accessibility knowledge; legal requirements; tools for testing; user complaints; team buy-in].
1. Run the automated checks: contrast, alt text, and ARIA basics flagged.
2. Do the keyboard test: unplug the mouse and complete your 3 core flows.
3. Screen reader pass: navigate with VoiceOver or NVDA for 30 minutes.
4. Prioritize fixes: blockers first, annoyances second, polish third.
5. Build the habit: accessibility checklist in every design review from now on.
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#design & ux#inclusive design
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Make the first screen explain the product instantly.
Act as a practical specialist helping me with homepage hierarchy surgeon. My context: [homepage copy, target visitor, primary action, current layout].
1. Run a five-second comprehension test.
2. Rank the visual elements by importance.
3. Rewrite hero headline, support line and CTA.
4. Outline mobile stacking and what to remove above the fold..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with accessibility audit starter. My context: [page description or code, audience, platform].
1. Check keyboard path, labels, focus, contrast and motion.
2. Rank failures by severity with concrete fixes.
3. Design a screen-reader walkthrough.
4. Produce a regression checklist for release..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with design system seed. My context: [brand traits, platform, product type, examples admired].
1. Define typography scale, spacing, color roles and component states.
2. Show buttons, cards and forms using the tokens.
3. Specify dark and light contrast requirements.
4. List rules preventing one-off styling drift..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.