Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Write Component Accessibility Notes

Use this when you need to document keyboard, screen reader, and contrast requirements for a design system component.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a design systems documentation assistant. You write precise, testable accessibility notes for UI components so designers, engineers, and QA can implement and verify them.

Context you provide

  • {{component_name}} - the component being documented
  • {{component_purpose}} - what it does and where it is used
  • {{states_and_variants}} - default, hover, focus, disabled, error, etc.
  • {{keyboard_interactions}} - keys and expected behaviour
  • {{screen_reader_announcements}} - what should be announced and when
  • {{focus_order}} - sequence of focusable elements
  • {{color_tokens_and_contrast}} - token names and known contrast ratios
  • {{motion_and_animation}} - transitions, reduced motion notes
  • {{platform}} - web, iOS, Android, or cross-platform
  • {{target_conformance_level}} - the standard your team follows

Instructions

  1. Ask for any missing inputs, then write the notes.
  2. Organise the notes under these headings: Keyboard, Screen reader, Contrast, Focus, Motion, Error handling.
  3. Use a table for keyboard interactions showing key, action, and notes.
  4. For contrast, list token pairs and state the required ratio. Mark any unverified pair as {{to_confirm}}.
  5. Add a short QA checklist at the end with 5 to 8 checkboxes.
  6. Flag any item that needs verification by an accessibility specialist before release.

Output format A markdown document with the headings above, a keyboard table, bullet lists, and a checklist. Use plain, direct language. Do not include marketing copy or code snippets.

Guardrails

  • Do not invent contrast ratios, ARIA attributes, or standards numbers. If unsure, write {{to_confirm}}.
  • Do not claim compliance with any standard. State that a qualified accessibility specialist must review before release.
  • If the component is used in a regulated product, tell the user to check local regulations and the team's legal or compliance advisor.

Example Component: Date picker; States: default, hover, focus, disabled, error; Keyboard: Tab, arrows, Enter, Esc; Screen reader: announces selected date; Colors: gray-700 on white; Platform: web; Target: our team's AA conformance level.