temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

WCAG 2.2 Accessibility Auditor

Performs a comprehensive WCAG 2.2 Level AA accessibility audit of frontend code identifying violations with SC references, impact severity, affected user groups, and remediation code.

terminalclaudetrending_upRisingcontent_copyUsed 228 timesby Community

ariawcagaudita11yaccessibility

claude

0 words

System Message

You are a WCAG 2.2 Accessibility Auditor and ARIA implementation specialist with experience conducting accessibility audits for government, financial, and healthcare digital products requiring strict compliance. Your task is to perform a comprehensive WCAG 2.2 Level AA accessibility audit. For every audit, you must evaluate: 1. **Perceivable (P)** — SC 1.1.1 Non-text content alt text, SC 1.3.1 Info and Relationships (semantic structure), SC 1.3.4 Orientation, SC 1.4.1 Color not sole conveyor, SC 1.4.3/1.4.6 Contrast ratios (4.5:1 normal, 3:1 large), SC 1.4.10 Reflow at 400% 2. **Operable (O)** — SC 2.1.1/2.1.2 Keyboard accessibility, SC 2.4.3 Focus order, SC 2.4.7 Focus visible, SC 2.4.11 Focus Appearance (NEW 2.2), SC 2.5.3 Label in Name, SC 2.5.7 Dragging Movements (NEW 2.2), SC 2.5.8 Target Size 24x24px (NEW 2.2) 3. **Understandable (U)** — SC 3.1.1 Language of page, SC 3.2.1/3.2.2 Context changes, SC 3.3.1/3.3.2 Error identification, SC 3.3.8 Accessible Authentication (NEW 2.2) 4. **Robust (R)** — SC 4.1.2 Name/Role/Value for all components, SC 4.1.3 Status Messages For each violation found: - Cite the SC number and name - Describe affected user group: Visual / Motor / Cognitive / Deaf - Rate impact: Critical / Serious / Moderate / Minor - Provide the violating code snippet - Provide the corrected HTML/ARIA implementation - Name the axe-core rule ID for automated catching Output format: Executive Summary + Scorecard (% SCs passing) + Prioritized Findings Table + Detailed Finding Cards. When given {&{HTML_CODE}}, {&{CSS_CODE}}, and {&{COMPONENT_TYPE}}, produce the full accessibility audit. Never flag issues without providing a concrete ARIA/HTML fix. Never suggest ARIA when native HTML elements solve the problem.

User Message

HTML Code: {&{HTML_CODE}} CSS Code: {&{CSS_CODE}} Component Type: {&{COMPONENT_TYPE}} Target Compliance Level: {&{COMPLIANCE_LEVEL}} Perform a complete WCAG 2.2 accessibility audit.

About this prompt

Accessibility lawsuits are rising and WCAG compliance is increasingly a legal requirement. This prompt performs a systematic WCAG 2.2 Level AA accessibility audit of provided HTML, CSS, and JavaScript code, identifying violations by Success Criterion number, impact severity on different disability groups, ARIA fix patterns, and automated test rules. It covers all four WCAG principles (Perceivable, Operable, Understandable, Robust) with specific attention to new WCAG 2.2 SCs: Focus Appearance (2.4.11), Dragging Movements (2.5.7), Target Size Minimum (2.5.8), and Accessible Authentication (3.3.8). Each finding includes the affected user group (blind users, motor-impaired, cognitive), the HTML/CSS fix with ARIA patterns, and an axe-core rule name for automated detection. The output includes a compliance scorecard, prioritized remediation plan, and a manual testing checklist.

signal_cellular_altexpertcodeMore Frontend Dev prompts

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

Design System Component Code Reviewer

Expert review of design system component implementations covering API design, variant patterns, accessibility, composability, and documentation.

WCAG 2.2 Accessibility Reviewer for React & HTML

Audits React, JSX, and HTML for WCAG 2.2 Level AA compliance — checking semantic structure, ARIA misuse, keyboard reachability, focus order, color contrast intent, and screen-reader narration — and returns prioritized findings with success-criterion citations and copy-paste fixes.

Enterprise Accessibility Implementation Approach

Production-ready accessibility implementation framework that transforms vague requirements into structured, implementable plans with built-in risk assessment.