Back to prompts
Coding & Developmentintermediate
4.7

Accessibility Auditor (WCAG 2.1)

Audit your website or app for accessibility issues — get specific fixes with code examples for WCAG compliance.

Copy & Paste this prompt
You are a web accessibility expert certified in WCAG 2.1 AA compliance. Audit my website/component for accessibility.

What to audit: [URL / OR PASTE YOUR HTML+CSS CODE]
Target compliance: [WCAG 2.1 AA / AAA]
Framework: [React / Vue / Angular / Plain HTML / OTHER]
User groups to consider: [BLIND / LOW VISION / MOTOR IMPAIRED / DEAF / COGNITIVE / ALL]

Deliver:

1. **QUICK SCAN RESULTS**
   - Critical issues (blocks access entirely) 🔴
   - Major issues (significant barriers) 🟡
   - Minor issues (improvements) 🟢
   - Pass rate estimate

2. **ISSUE DETAILS** (for each issue)
   - What's wrong (specific element/component)
   - Which WCAG criterion it violates (number + name)
   - Who it affects and how
   - How to fix it (with code before/after)
   - Priority (must fix vs should fix)

3. **COMMON PATTERNS TO CHECK**
   - Color contrast (text on backgrounds)
   - Keyboard navigation (can everything be reached?)
   - Screen reader experience (are labels correct?)
   - Focus management (modals, dynamic content)
   - Image alt text (descriptive, not 'image.jpg')
   - Form labels and error messages
   - Touch targets (minimum 44x44px)

4. **TESTING CHECKLIST**
   - Manual tests to perform (keyboard-only navigation)
   - Screen reader test script (what to check with NVDA/VoiceOver)
   - Tools to use (axe, Lighthouse, WAVE)
   - Automated test code (jest-axe or similar)

5. **IMPLEMENTATION GUIDE**
   - ARIA attributes cheat sheet for common components
   - Accessible component patterns (dropdown, modal, tabs, accordion)
   - Skip links and landmark structure

Paste my code:
```
[YOUR HTML/JSX HERE]
```
#accessibility#wcag#a11y#web-development#inclusive-design

Works with

chatgptclaudegemini

💡 Pro Tips

  • Try navigating your site with only a keyboard — you'll find issues fast
  • Color contrast is the most common and easiest fix
  • Accessibility benefits everyone — not just people with disabilities

🧠 Why This Works

Accessibility issues affect 15-20% of users and create legal liability. This prompt applies WCAG 2.1 success criteria systematically to identify barriers that automated tools miss—like focus management, screen reader announcements, and keyboard navigation patterns.

📅 When to Use This Prompt

Use when auditing a web application for accessibility compliance, when preparing for an accessibility certification or legal requirement, or when you want to ensure your UI is usable by people with disabilities before launch.

🎯 What You'll Get

You'll get a prioritized list of accessibility violations with WCAG success criterion references, specific code fixes for each issue, testing instructions for screen readers and keyboard navigation, and ARIA attribute recommendations.

🔗 Related Prompts

Coding & Development

Senior Engineer Code Review

Get a thorough code review as if a senior engineer is looking at your PR — bugs, patterns, performance, and suggestions.

code-reviewbest-practicessecurity
4.9
intermediate
Creative ThinkingPremium

UI Wireframe to Developer Spec

Describe UI wireframes in such detail that developers can implement them pixel-perfect without Figma.

UI-designwireframedeveloper-spec
4.7
advanced