Create a WCAG 2.2 AA Accessibility Audit Checklist

Receive a structured accessibility audit checklist for complex interactive components based on WCAG 2.2 AA standards.

Prompt

Prompt
Act as an Accessibility Auditor. Your job is to create a detailed WCAG 2.2 AA audit checklist for a specific interactive component. First, ask me these three questions: 1. What is the component (e.g., a multi-select dropdown, date picker, or data table)? 2. What is the primary user interaction (e.g., mouse click, keyboard navigation, drag-and-drop)? 3. Are there any specific mobile-responsive constraints? After I answer, provide a table that covers keyboard focus, ARIA attributes, screen reader announcements, and visual states. Rules: 1. Each row must define a pass/fail criterion. 2. Reference specific WCAG 2.2 success criteria codes. 3. Use plain language for testing instructions. 4. Include a final column for notes on remediation. Output format: ## Accessibility Audit Checklist for [Component Name]. A markdown table with columns: Category, Success Criteria, Testing Instruction, Pass/Fail Criteria, and Remediation Notes. This checklist is not professional accessibility consulting advice; consult a certified accessibility specialist for compliance certification.

Example output

At a glanceDate picker accessibility audit checksFour WCAG 2.2 AA checks, each with a test and a fix
  1. Keyboard Focus2.1.1Tab and Arrow keys show a visible focus indicator
  2. ARIA Attributes4.1.2Grid role and gridcell roles; label names month and year
  3. Screen Reader4.1.3Date label and state announced; add aria-live region
  4. Visual States1.4.11Selected date keeps 3:1 contrast against background

Example for: a custom date picker component used in a booking system. ## Accessibility Audit Checklist for Date Picker | Category | Success Criteria | Testing Instruction | Pass/Fail Criteria | Remediation Notes |
| :--- | :--- | :--- | :--- | :--- |
| Keyboard Focus | 2.1.1 Keyboard | Navigate through dates using Tab and Arrow keys. | Focus indicator is visible on the current date and date cells. | Add CSS outline for focus state. |
| ARIA Attributes | 4.1.2 Name, Role, Value | Inspect element role for date grid. | Role is set to grid and cells have role gridcell. | Ensure aria-label identifies the month and year. |
| Screen Reader | 4.1.3 Status Messages | Open picker and navigate to a date. | Screen reader announces the date label and state. | Add aria-live region for date selection updates. |
| Visual States | 1.4.11 Non-text Contrast | Check contrast of selected vs unselected dates. | Selected date maintains 3:1 contrast ratio against background. | Adjust blue background opacity to meet contrast. | This checklist is not professional accessibility consulting advice; consult a certified accessibility specialist for compliance certification.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Forces a structured, table-based output that is easy for developers to track.
  • Ensures compliance by linking every item to specific WCAG 2.2 criteria.
  • Includes a clear disclaimer regarding professional certification.

Use this prompt to build a testing plan for developers or designers. It works best in ChatGPT, Claude, or Gemini. Paste the component details when the model asks, or provide them upfront if you prefer.

Common edits

  • Change the scope to focus only on mobile if you are building a mobile-first app.
  • Add a column for browser-specific testing if you support legacy environments.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Design