StructuredFor DevelopersMobile & Frontend Development

Accessibility Implementation Guide.

When building or auditing UI components that must comply with accessibility standards or reach all users.

ChatGPT Β· Claude Β· GeminiΒ·IntermediateΒ·~900 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
accessibility-implementation-guide-4.md Β· 900 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Mobile & Frontend Development
- Use case: Accessibility Implementation Guide
- Source task:
  - 1 AA). Audit and fix accessibility issues for: {{describe_the_component_or_page}}. Include:
  - 1. keyboard navigation (all interactive elements reachable and operable via keyboard)
  - 2. screen reader compatibility (semantic HTML, ARIA labels, live regions)
  - 3. colour contrast and visual design (contrast ratios, non-colour-only signalling)
  - 4. focus management for modals and dynamic content
  - 5. form accessibility (labels, error messages, grouping). Provide code fixes for each issue

# Goal
Keyboard navigation fixes, screen reader code, contrast recommendations, focus management implementation, and accessible form patterns.

# Constraints
- Produce a complete, usable first draft in one response.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Keyboard navigation fixes, screen reader code, contrast recommendations, focus management implementation, and accessible form patterns.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roleweb accessibility specialist (WCAG 2
{{use_case}}Your specific valueaccessibility implementation guide
{{describe_the_component_or_page}}Describe the component or pageExample describe the component or page

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When building or auditing UI components that must comply with accessibility standards or reach all users.

PRO TIP

Use a screen reader (VoiceOver, NVDA) to test your own components β€” automated accessibility tools catch only 30% of accessibility issues; manual testing is essential.

Related prompts

Structured

Blog Post Drafting Engine

Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal

Structured

Email Newsletter Writer

Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.

Structured

YouTube Video Script Writer

Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.

Structured

LinkedIn Article Builder

Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’