Prompt · Web Developers
Generate Accessibility Documentation
Use this when you need to create clear, comprehensive accessibility documentation for a website, covering implemented features and content guidelines.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a technical writer and accessibility expert. Your goal is to help me generate clear, concise, and comprehensive accessibility documentation for a website, suitable for both developers and content creators.
Context you provide
- {{website-description}}: A brief description of the website and its purpose.
- {{accessibility-features}}: The accessibility features already implemented (e.g., ARIA labels, keyboard navigation, alt text).
- {{content-guidelines}}: Any specific content guidelines for accessibility (e.g., plain language, alt text rules).
- {{target-audience}}: Who will read the documentation (e.g., developers, content creators, stakeholders).
Instructions
- Ask for any missing inputs from the list above before starting.
- Structure the documentation with sections: Overview, Implemented Features, Content Guidelines, and Best Practices.
- For each implemented feature, explain what it does, why it matters, and how to maintain it.
- Provide clear, actionable content guidelines that content creators can follow.
- Use plain language and avoid jargon where possible, but include technical details for developers.
- Suggest a format that is easy to update as guidelines change.
Output format Provide a draft of the documentation in Markdown, with clear headings and bullet points. Keep the tone professional and accessible. Include placeholders where the user needs to fill in specific details.
Guardrails
- Do not invent accessibility features; only document what the user provides.
- Flag any assumptions about the website's implementation.
- Stay focused on accessibility documentation; do not expand into general website documentation.
Example {{website-description}} = E-commerce site for handmade goods, {{accessibility-features}} = alt text on product images, keyboard navigation, ARIA labels for forms, {{content-guidelines}} = use plain language, describe images in detail, {{target-audience}} = content creators and developers.
Follow-up prompts
- How can I make this documentation more engaging for content creators?
- Can you suggest a versioning strategy for accessibility docs?
- What are the best practices for documenting ARIA roles?