UI/UX Design

Accessibility Audit Checklist Generator

Input your product URL or description and get a comprehensive WCAG accessibility audit checklist with specific tests, tools, and fix recommendations.

By The Prompt Black Magic Team

Paste into any LLM with your product details. Use the output as a structured audit framework for your team.

You are a certified accessibility specialist (IAAP CPAC) who has audited products for WCAG 2.2 compliance for government agencies and Fortune 500 companies.

Product type: [WEBSITE/WEB APP/MOBILE APP/DESKTOP APP]
Tech stack: [REACT/ANGULAR/VUE/NATIVE/OTHER]
Current compliance level: [UNKNOWN/PARTIAL/AIMING FOR AA/AIMING FOR AAA]
User base: [CONSUMER/ENTERPRISE/GOVERNMENT/HEALTHCARE/EDUCATION]
Priority areas: [VISUAL/MOTOR/COGNITIVE/AUDITORY/ALL]

Create a complete accessibility audit plan:

**1. Automated Testing Setup**
- Tools to run: axe-core, Lighthouse, WAVE, Pa11y
- Configuration for each tool
- CI/CD integration instructions
- How to interpret results and prioritize
- Common false positives to ignore

**2. Manual Testing Checklist (by WCAG principle)**

Perceivable:
- [ ] All images have meaningful alt text
- [ ] Color is not the only way information is conveyed
- [ ] Text contrast meets 4.5:1 (AA) or 7:1 (AAA)
- [ ] Content is readable at 200% zoom
- [ ] Video has captions and audio descriptions
- [ ] Content structure uses proper heading hierarchy
(Continue for all Perceivable criteria)

Operable:
- [ ] All functionality works with keyboard only
- [ ] Focus order is logical and visible
- [ ] No keyboard traps
- [ ] Skip navigation link exists
- [ ] Timing is adjustable or not required
- [ ] No content flashes more than 3 times per second
(Continue for all Operable criteria)

Understandable:
- [ ] Language is declared in HTML
- [ ] Form labels are associated with inputs
- [ ] Error messages identify the field and suggest fixes
- [ ] Navigation is consistent across pages
- [ ] Input purpose is identified for autofill
(Continue for all Understandable criteria)

Robust:
- [ ] Valid HTML markup
- [ ] ARIA roles and properties used correctly
- [ ] Custom components have proper roles and states
- [ ] Status messages use ARIA live regions
(Continue for all Robust criteria)

**3. Assistive Technology Testing**
- Screen reader testing script (VoiceOver, NVDA, JAWS)
- Screen magnifier testing steps
- Voice control testing (Dragon, Voice Control)
- Switch access testing
- Specific scenarios to test for each AT

**4. Remediation Priority Matrix**
- Critical (legal risk, blocks users): fix immediately
- High (significant barriers): fix in current sprint
- Medium (usable but difficult): fix in next sprint
- Low (best practices): backlog

**5. Ongoing Compliance**
- Component library accessibility checklist
- Designer handoff requirements
- Developer review checklist
- QA accessibility test cases
- Voluntary Product Accessibility Template (VPAT) prep

For each checklist item: include the specific WCAG criterion number, how to test it, what passing looks like, and a code example of the fix.

When to Use This Prompt

Expected Results

How to Customize This Prompt