Skip to main content
Design & UI/UXAccessibilityadvanced

WCAG 2.2 AA Accessibility & Inclusive Design Compliance Audit

Optimized for Claude, Chatgpt, Gemini • Verified Prompt Template

Audit digital interfaces for WCAG 2.2 AA compliance, color contrast, keyboard focus, and screen reader UX.

Compatibility & Specs

Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedOct 3, 2026
Customizable Variables4 parameters

How to Use This Prompt

Follow this 3-step workflow to extract high-signal responses from any compatible AI model.

01

1. Tailor the Parameters

Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.

02

2. Send to AI Model

Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.

03

3. Review and Iterate

Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.

Prompt Variables & Parameters

Reference breakdown of every dynamic variable embedded in this prompt template.

PlaceholderParameter NameTypeStatusDescription & Guidance
[component_description]Component & User InteractiontextRequiredWhat the component does and how users engage with itDefault: A collapsible accordion FAQ component that toggles answers when headers are clicked.
[code_markup]Current HTML / React CodetextareaRequiredThe markup or React JSX to auditDefault: <div className="accordion-item"> <div className="accordion-header" onClick={() => setIsOpen(!isOpen)}> <span className="text-gray-400">{title}</span> <i className={isOpen ? "icon-chevron-up" : "icon-chevron-down"} /> </div> {isOpen && <div className="accordion-content text-gray-500">{content}</div>} </div>
[color_tokens]Color Palette & Text ColorstextRequiredForeground text hex, background hex, border colorsDefault: Header text: #9CA3AF on white #FFFFFF background. Content text: #6B7280 on white background.
[interaction_patterns]Keyboard & Touch PatternstextRequiredHow users currently interact using keyboard or touchDefault: Users click with mouse or tap screen. It is not currently focusable via Tab key.

Example Output & Parameters Breakdown

Inspect verified benchmark AI responses and review how parameters, system constraints, and input variables calibrate generation.

Parameters & Variable Breakdown

4 Inputs
[component_description]
A collapsible accordion FAQ component that toggles answers when headers are clicked.
[code_markup]
<div className="accordion-item"> <div className="accordion-header" onClick={() => setIsOpen(!isOpen)}> <span className="text-gray-400">{title}</span> <i className={isOpen ? "icon-chevron-up" : "icon-chevron-down"} /> </div> {isOpen && <div className="accordion-content text-gray-500">{content}</div>} </div>
[color_tokens]
Header text: #9CA3AF on white #FFFFFF background. Content text: #6B7280 on white background.
[interaction_patterns]
Users click with mouse or tap screen. It is not currently focusable via Tab key.

Verified AI Benchmark Response

Grounded Output
### WCAG 2.2 AA Accessibility Audit: Collapsible Accordion #### 1. Critical Violations Identified * **Fails WCAG 2.1.1 (Keyboard Navigation - Level A):** The header uses `<div onClick>` with no `tabIndex="0"` or keyboard event listeners (`Enter` / `Space`). Keyboard-only and assistive device users cannot trigger the accordion. * **Fails WCAG 4.1.2 (Name, Role, Value - Level A):** Screen readers announce a generic non-interactive text block. It lacks `role="button"`, `aria-expanded="true|false"`, and `aria-controls`. * **Fails WCAG 1.4.3 (Contrast Minimum - Level AA):** `#9CA3AF` on `#FFFFFF` yields a contrast ratio of only **2.85:1**, severely below the mandatory **4.5:1** threshold for normal text. #### 2. Accessible Semantic Replacement ```tsx import { useId, useState } from "react"; import { ChevronDown } from "lucide-react"; interface AccordionProps { title: string; content: string; } export function AccessibleAccordion({ title, content }: AccordionProps) { const [isOpen, setIsOpen] = useState(false); const contentId = useId(); const buttonId = useId(); return ( <div className="border-b border-border py-2"> <h3> <button id={buttonId} type="button" aria-expanded={isOpen} aria-controls={contentId} onClick={() => setIsOpen((prev) => !prev)} className="flex w-full items-center justify-between py-3 text-left font-medium text-foreground hover:text-primary focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-primary focus-visible:ring-offset-2" > <span>{title}</span> <ChevronDown className={`h-4 w-4 shrink-0 transition-transform duration-200 text-foreground ${ isOpen ? "rotate-180" : "" }`} aria-hidden="true" /> </button> </h3> <div id={contentId} role="region" aria-labelledby={buttonId} hidden={!isOpen} className="pb-4 text-sm text-muted-foreground leading-relaxed" > {content} </div> </div> ); } ```

Best Use Cases

Scenarios and roles where this prompt produces maximum leverage.

Frontend teams preparing websites for corporate accessibility compliance audits
UI designers ensuring high-contrast palettes meet legal standards
QA engineers testing keyboard traps and ARIA states before production launch

Tips for Best Results

Techniques to elevate response fidelity

  • •Provide rich background context rather than one-sentence inputs to receive deep, non-generic responses.
  • •Engage in multi-turn conversation: use the initial output as a baseline, then ask the AI to sharpen specific sections.
  • •Prompt the model to highlight any hidden assumptions or missing trade-offs in its recommendations.

Common Mistakes to Avoid

Frequent failure modes and anti-patterns

  • •Giving minimal context and expecting nuanced, expert-level strategic output.
  • •Not validating factual references, citations, or statistical claims with verified primary sources.
  • •Skipping the customization step and pasting raw bracketed template variables into the AI chat.

Frequently Asked Questions About This Prompt

Technical guidance on model compatibility, parameter substitution, iteration techniques, and commercial usage.

Q1.Which AI models work best with the "WCAG 2.2 AA Accessibility & Inclusive Design Compliance Audit" prompt?

This prompt is thoroughly tested and compatible with Claude, Chatgpt, Gemini. For multi-step reasoning, architectural planning, and code refactoring, Claude 3.7/3.5 Sonnet and ChatGPT-4o provide the highest constraint adherence. For large-document synthesis, Google Gemini 2.5 Pro is also recommended.

Q2.How do I customize the parameters in this prompt template?

This template features 4 customizable parameter(s): [component_description], [code_markup], [color_tokens], [interaction_patterns]. Replace each bracketed placeholder with your project's specific details, constraints, or code before submitting to your AI model. You can also use our interactive workbench on this page to populate and copy the completed prompt in one click.

Q3.Can I use this prompt and its outputs for commercial projects?

Yes. All prompts published on Beautiful AI Prompt are 100% free for both personal and commercial use. You hold full ownership of all code, copy, strategies, or imagery generated by your selected AI model when running this prompt.

Q4.How does this prompt prevent AI hallucinations and ensure output accuracy?

This template enforces explicit negative constraints, few-shot parameter boundaries, and schema requirements (such as tabular comparisons or step-by-step logic). This suppresses speculative drift and forces the AI model to ground its response in your provided inputs.

Part of Curated Collections

This prompt is sequenced as part of these goal-oriented workflows

View all collections

Related AI Prompts

Complementary workflows in Design & UI/UX

View all Design & UI/UX prompts
Design & UI/UXintermediate

UI Design Visual Hierarchy, Contrast & Spatial Rhythm Critique

Conduct an objective, rigorous visual critique of a digital interface layout, typography, and density.

[Copy & Paste Template]4 parameters

›You are a Principal Product Designer and Design Systems Architect. Review the following interface layout and design specifications with objective, actionable rigor. Avoid subjective praise or vague advice like 'make it cleaner'. Evaluate it against fundamental design laws: visual hierarchy, spatial rhythm (8pt grid), typographic contrast, visual weight, and interaction affordance. Product Type & Primary User Goal: [product_context] Current Screen / Component Layout & Hierarchy: [screen_layout] Color Palette & Typography System: [design_tokens] Known Usability Concerns or Friction Points: [usability_concerns] Deliver a Systematic UI Design Critique: 1. Visual Hierarchy & Eye-Scanning Flow: Map the viewer's likely scanning path (Z-pattern or F-pattern). Identify visual competition where secondary elements distract from the primary call-to-action. 2. Typography Scale & Density: Audit font sizes, line heights, weights, and letter-spacing. Flag issues where text lacks distinct contrast or causes visual vibration. 3. Spatial Rhythm & Alignment: Evaluate padding, margins, and layout alignment against a strict 4px/8px grid system. Point out uneven whitespace, claustrophobic elements, or disconnected groupings. 4. Action Hierarchy & Affordance: Evaluate primary, secondary, and tertiary button states. Ensure interactive elements look clickable and disabled states don't cause confusion. 5. Specific Prescriptive Redesign Blueprint: Provide precise CSS/Tailwind values or spatial adjustments to elevate the UI to a world-class, premium aesthetic.

claudechatgptgemini
#design#ui-critique#visual-hierarchy
Design & UI/UXadvanced

Design System Semantic Token Architecture & Component Matrix

Architect scalable design tokens (color, spacing, typography) and component variant matrices.

[Copy & Paste Template]4 parameters

›You are a Principal Design Systems Architect bridging UI design (Figma) and modern frontend code (CSS Variables, Tailwind CSS, Radix UI). I need to design a scalable design system foundation for a multi-platform product. Brand Identity & Product Domain: [brand_context] Theming & Dark Mode Requirements: [theme_requirements] Core Components in Scope: [component_scope] Frontend Framework & Styling Engine: [tech_stack] Deliver the Comprehensive Design System Architecture Plan: 1. 3-Tier Token Architecture: Structure the design tokens systematically: - Primitives (Global / Raw Values: slate-500, blue-600, 16px) - Semantics (Purpose-driven: surface-primary, text-muted, border-interactive) - Component-Specific (btn-primary-bg, input-focus-ring) 2. Dark Mode Elevation & Contrast Token Strategy: Define how surfaces, borders, and shadows behave between light and dark themes without relying on inverted pure black/white. 3. Component Variant Matrix: For the requested core components, document the exact props, variant names (`default`, `secondary`, `destructive`, `ghost`), sizes (`sm`, `md`, `lg`), and interactive states (`hover`, `focus-visible`, `active`, `disabled`, `loading`). 4. CSS Variable / Tailwind v4 Configuration: Provide the exact CSS variable definitions (in OKLCH or HSL) and Tailwind utility mappings ready to paste into `globals.css`.

claudechatgptgemini
#design#design-systems#tokens
Reactadvanced

React Component Composition & Compound Component Architecture Review

Refactor bloated prop-drilling components into clean, composable compound components with flexible layouts.

[Copy & Paste Template]3 parameters

›You are a Principal Frontend Architect and Design System Lead. I have a monolithic, brittle React component that has accumulated too many boolean flags and needs to be refactored into a composable Compound Component architecture. Current Bloated Component Code & Props Interface: [bloated_component_code] Desired Consumer Flexibility / Layout Variations: [desired_flexibility] State & Event Coordination Needed Across Sub-Components: [state_coordination] Perform a Component Architecture Overhaul: 1. Prop Explosion & Coupling Antipatterns: Detail why the current design violates the Open-Closed Principle (e.g. `showIcon`, `isModal`, `hasBorder`, `buttonPosition` flags). 2. Compound Component API Design: Define the clean JSX consumer usage syntax showing how sub-components (e.g. `<Card.Header>`, `<Card.Body>`, `<Card.Footer>`, `<Card.Action>`) compose together naturally. 3. TypeScript & Context Implementation: Write the complete, production-ready implementation using an internal React Context, custom hook (`useCardContext`), and strict TypeScript typing for sub-components. 4. Keyboard Navigation & ARIA Binding: Ensure internal context coordinates required WAI-ARIA states (e.g. `aria-expanded`, `aria-controls`) seamlessly across sub-components.

claudechatgptgemini
#react#compound-components#component-architecture