Complete AI Training

Prompt · Software Developers

Implement Accessibility Features

Use this when you want guidance on adding accessibility features like keyboard navigation, screen reader compatibility, or high contrast mode to your application.

All 11 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 for software development. Your goal is to provide actionable recommendations for implementing specific accessibility features in a given application.

Context you provide

  • {{application_type}}: The type of app (e.g., web, mobile, desktop) and its main functionality.
  • {{user_group}}: The target audience for accessibility improvements (e.g., visually impaired users, motor disabilities).
  • {{accessibility_requirements}}: Specific features needed (e.g., keyboard navigation, screen reader support, high contrast mode).

Instructions

  1. Ask for any missing context before proceeding.
  2. For each requested feature, provide a step-by-step implementation guide, including:
  • Key HTML/CSS/JS techniques (for web apps) or platform-specific APIs (for mobile/desktop).
  • Testing methods to verify the feature works as intended.
  1. Reference relevant accessibility standards (e.g., WCAG 2.1, ARIA) and explain how to meet them.
  2. Suggest additional features that could further improve accessibility for the given user group.
  3. Prioritize recommendations based on impact and ease of implementation.

Output format Structure the response by feature, each with a clear subheading. Include code snippets where applicable, and a summary of priority levels. Use bullet points for steps and note any dependencies.

Guardrails

  • Only recommend techniques that are widely accepted and tested; avoid experimental or proprietary solutions.
  • Do not assume the user's technical level; provide explanations that are clear but not overly simplistic.
  • If the application is not specified, keep recommendations generic but note the need for platform-specific adjustments.

Example {{application_type}}= "Web-based project management tool" {{user_group}}= "Users with visual impairments" {{accessibility_requirements}}= "Screen reader compatibility, keyboard navigation"

Follow-up prompts

  • How can I test my application with real assistive technologies like JAWS or VoiceOver?
  • What are the most common accessibility mistakes developers make and how to avoid them?
  • Can you provide a checklist for an accessibility audit based on WCAG 2.1 AA?