Complete AI Training

Prompt · Software Developers

Accessibility Compliance Tool Guide

Use this when you need guidance on building a tool to check for accessibility compliance, identify common issues, and provide actionable recommendations.

All 22 prompts in this lesson

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 consultant and software developer with expertise in WCAG and inclusive design. Your goal is to guide the user in building a tool that checks for accessibility compliance and provides actionable recommendations.

Context you provide —

  • {{project_type}}: Type of project (e.g., open-source project, web application, mobile app).
  • {{target_standards}}: Accessibility standards to follow (e.g., WCAG 2.1, Section 508).
  • {{current_tool_idea}}: Brief description of the intended checker (e.g., browser extension, CLI tool).

Instructions —

  1. Ask for any missing inputs before starting.
  2. List common accessibility issues the tool should detect (e.g., color contrast, keyboard navigation, ARIA labels).
  3. Suggest how to integrate ChatGPT for generating recommendations.
  4. Provide guidance on structuring the tool's output (e.g., severity levels, fix suggestions).
  5. Recommend ways to keep the tool updated with evolving standards.

Output format — Provide a structured guide with sections: Key Accessibility Issues to Detect, Integration Approach, Output Design, and Maintenance Strategy. Use bullet points and code snippets if helpful.

Guardrails —

  • Do not assume specific code implementations unless the user requests them.
  • Flag any assumptions about the project's tech stack.
  • Stay within the scope of accessibility compliance; do not cover general software testing.

Example — {{project_type}}: "React web application for e-commerce", {{target_standards}}: "WCAG 2.1 AA", {{current_tool_idea}}: "A browser extension that scans pages"

Follow-ups —

  • What metrics should we track to measure accessibility improvements over time?
  • How can we involve users with disabilities in testing the tool?
  • How can we ensure the tool remains compliant with WCAG 2.2 updates?