AI prompts that catch what a quick glance won't.
Paste your code, a component, or a workflow into these prompts and run them in whatever AI tool you already use (ChatGPT, Claude, Copilot). Organised by WCAG 2.2 principle, so you know exactly what each one is checking, and why it's in scope for EAA compliance. Every prompt below is copyable with one click.
These prompts are a starting point, not a substitute for testing with real assistive technology or a manual audit. AI output can miss context and occasionally get specifics wrong, always verify against the actual WCAG success criterion.
WCAG Principle 1: can it be perceived at all?
Headings, alt text, and contrast are the foundation, get these wrong and nothing else in the audit matters.
Heading Hierarchy Audit
Analyze this HTML code snippet and check if the headings follow a strict, logical hierarchy (e.g., no skipping from H2 to H4). Rewrite it using semantic HTML5 elements if any errors are found.
Alt Text Generator
SC 1.1.1Review these image descriptions and context parameters. Generate descriptive, concise alt text that fulfills WCAG 2.2 SC 1.1.1. If an image is purely decorative, provide the exact code format to hide it from screen readers.
Color Contrast Checker
SC 1.4.3Calculate the contrast ratio for a text color of [HEX_CODE] on a background color of [HEX_CODE]. Does it meet WCAG 2.2 SC 1.4.3 Level AA requirements for normal text (4.5:1) and large text (3:1)? If not, suggest the closest compliant HEX alternatives.
WCAG Principle 2: can it be operated without a mouse?
Every interaction that only works on click, hover, or drag is a barrier for keyboard and switch-device users.
Keyboard Navigation Strategy
Analyze this custom interactive UI component (e.g., dropdown menu/modal). Identify potential keyboard traps and rewrite the JavaScript/CSS to ensure full keyboard operability, explicit focus indicators, and correct sequential tab order.
Interactive Elements Fix
Review this code block. Replace all clickable non-interactive elements (like <div> or <span> click handlers) with semantic native HTML buttons or links. Ensure correct anchor attributes are present and remove positive tabindexes.
Touch Target & Spacing Optimization
SC 2.5.8Review this CSS component layout. Check if all interactive touch targets meet the WCAG 2.2 SC 2.5.8 Target Size minimum requirement of 24x24 CSS pixels (or WCAG 2.1 44x44 pixels). Provide updated CSS to meet compliance.
WCAG Principle 3: does the user know what went wrong?
Unlabeled fields and silent validation errors are two of the most common reasons a checkout flow gets flagged.
Form Field Association
Audit this HTML form snippet. Ensure every single user input element is properly and explicitly associated with a <label> element or possesses valid ARIA labeling attributes. Rewrite the code to fix any unlabeled elements.
Error Handling & Form Validation
SC 3.3.1 / 3.3.3Write a frontend validation script for this form that complies with WCAG 2.2 SC 3.3.1 (Error Identification) and SC 3.3.3 (Error Suggestion). The script must provide clear, text-based error messages and programmatically announce them to assistive technologies.
WCAG Principle 4: does it hold up in real assistive tech?
Custom components and dynamic content are where markup that looks fine visually breaks down for screen reader users.
ARIA Name and Role Validation
Examine this complex UI component. Verify that all custom ARIA roles, states, and properties match their exact operational behavior. Check if the element exposes a proper accessible name and role to screen readers.
Dynamic Content Announcements
Review this dynamic Single Page Application (SPA) element (e.g., toast notification, live search results). Provide the code necessary to use ARIA live regions so that status updates are instantly announced to screen reader users without shifting their focus.
Beyond code: the paperwork regulators ask for
Technical fixes aren't the whole file. An accessibility statement and reachable support channels are part of what the EAA actually requires.
Accessibility Statement Drafting
Act as a digital compliance expert. Draft a public Accessibility Statement template tailored for an e-commerce platform that aligns with EAA and EN 301 549 requirements. Include placeholders for compliance status, feedback mechanisms, and dedicated support channels.
Support Channel Review
Review our customer support architecture workflow. Does it provide the necessary alternative communication channels (e.g., text-based assistance alongside phone lines) required under the European Accessibility Act's functional performance mandates?
The rest is legal, not just technical.
These prompts catch a lot of what an AI tool can see in your code. What they can't do is confirm your organisation's EAA obligations, deadlines, or how a Formal Notice actually gets resolved. Learn more about the technical alignments, timeline deadlines, and organizational obligations.