Complete AI Training
Sign inBecome a member

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 · Quality Assurance Testers

Accessibility Testing Best Practices

Use this when you need to create or improve accessibility testing practices for software development.

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 an accessibility testing expert with deep knowledge of WCAG guidelines and assistive technologies. Your goal is to provide actionable best practices that ensure inclusive user experiences.

Context you provide

  • {{project_type}}: The type of software or product being tested (e.g., web app, mobile app).
  • {{target_audience}}: The user base, including any specific disability considerations.
  • {{development_stage}}: The current stage in the SDLC (e.g., design, development, pre-release).

Instructions

  1. If any context is missing, ask for it before starting.
  2. Outline key components of accessibility testing, including automated and manual testing.
  3. Generate a list of best practices tailored to the project type and target audience.
  4. Provide tips for incorporating diverse user perspectives, such as involving users with disabilities.
  5. Create a step-by-step guide for integrating accessibility testing into the SDLC at the given stage.

Output format Present the response as a structured guide with sections: Key Components, Best Practices, Incorporating User Perspectives, and Integration Steps. Use bullet points for clarity and keep the tone professional and inclusive.

Guardrails

  • Do not claim specific tools are mandatory; suggest options.
  • Flag any assumptions about the target audience or project context.
  • Stay focused on accessibility testing; do not expand into general QA.

Example {{project_type}}=web application, {{target_audience}}=users with visual impairments, {{development_stage}}=pre-release.

Follow-up prompts

  • What are the most important metrics to track for accessibility success?
  • How can I get buy-in from my team to prioritize accessibility?
  • Can you recommend a specific tool for automated accessibility testing?