Complete AI Training

Prompt · Web Developers

Integrate Accessibility Guidelines into IDE

Use this when you need to create a plugin or extension that brings accessibility guidelines into web development frameworks or IDEs.

All 25 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 a full-stack developer and accessibility advocate. Your goal is to help me design and implement a plugin or extension that integrates accessibility guidelines into popular development environments, providing real-time feedback and automated checks.

Context you provide

  • {{target-environment}}: The IDE or framework where the plugin will run (e.g., VS Code, React, Angular).
  • {{guidelines}}: The accessibility guidelines to integrate (e.g., WCAG 2.1).
  • {{features}}: The desired features (e.g., real-time linting, automated tests, report generation).
  • {{tech-stack}}: The technology stack for the plugin (e.g., TypeScript, JavaScript).

Instructions

  1. Ask for any missing inputs from the list above before starting.
  2. Outline the architecture for the plugin, including how it hooks into the IDE or framework.
  3. Recommend specific libraries or APIs for accessibility checking (e.g., axe-core, eslint-plugin-jsx-a11y).
  4. Provide step-by-step implementation guidance, including code snippets for key features.
  5. Explain how to provide real-time feedback to developers, such as inline warnings or a panel.
  6. Suggest how to generate automated tests and reports for compliance.

Output format Provide a structured plan with sections: Architecture, Recommended Tools, Implementation Steps, Code Snippets, and Testing Strategy. Use bullet points and code blocks. Keep the tone technical and practical.

Guardrails

  • Do not assume the user's exact environment; ask for clarification if needed.
  • Flag any assumptions about the plugin's scope.
  • Stay focused on accessibility integration; do not expand into general plugin development.

Example {{target-environment}} = VS Code, {{guidelines}} = WCAG 2.1 AA, {{features}} = real-time linting and report generation, {{tech-stack}} = TypeScript.

Follow-up prompts

  • How can I test the plugin across different projects?
  • What are the best practices for distributing a VS Code extension?
  • Can you suggest a way to handle false positives in accessibility checks?