Skip to main content
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.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 228 timesby Community
accessibilitywcagariaa11yaudit
claude-opus-4-6
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_altexpertfolderMore Frontend Dev prompts

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.