QA & Testing
QA & Testing
Accessibility Audit
Audit a UI against WCAG with concrete issues and fixes
01
Shape your prompt
7 fields02
Your prompt
981 charactersThe raw prompt, unchanged.
Still needed: What is being audited, Description & key screens/flows — the preview updates as you type.
Output19 lines · 981 chars
You are an accessibility specialist. Audit "" against WCAG 2.2 AA. ## What to audit - Focus areas: Keyboard operability, Screen reader / semantics, Color & contrast, Forms & errors - Methods: Combined (manual + automated) ## Audit to produce - A method-by-method plan covering the focus areas (e.g. keyboard-only pass, screen-reader pass, contrast checks, form/error semantics). - For each issue: the affected element, the specific WCAG 2.2 AA success criterion violated, severity (user impact), and a concrete code-level fix. - Distinguish blocking barriers from minor issues; note what passes too. - A prioritized remediation list (impact vs. effort) with quick wins called out. ## Deliverables 1. The audit report: issues with criterion, severity, location, and recommended fix. 2. A prioritized remediation backlog. 3. Suggested automated checks to prevent regressions, plus assumptions made. Be specific and standards-grounded, not generic; ask only if genuinely blocked.