ai-accessibility-auditlisted

# AI Accessibility Audit Catch accessibility regressions in AI product surfaces *before* they ship - chat interfaces, agent dashboards, generated-content panels, streaming output regions, and consent / safety UI. WCAG 2.2 Level AA is the bar; the framework below operationalizes it for AI-specific patterns that the spec doesn't natively cover. ## Core Principle Accessibility is a property of the *experience*, not just the markup. An AI product can pass an axe-core scan and still be unusable for a screen-reader user if streaming output isn't announced, consent UI traps focus, or "regenerate" controls are unreachable from the keyboard. This skill audits both the static layer (DOM, contrast, semantics) and the AI-specific dynamic layer (live regions, latency, motion). --- ## The CLEAR Audit Framework | Letter | Dimension | The Question | |--------|-----------|--------------| | **C** | Contrast & Color | Does every text/icon/state meet 4.5:1 (or 3:1 for ≥18pt or non-text UI)? Is color the *only* signal anywhere? | | **L** | Logic of Focus | Can a keyboard-only user reach every action in a sensible order, with a visible focus indicator and no traps? | | **E** | Equivalents for Non-Text | Do images, charts, generated visuals, and audio have meaningful alternatives - including AI-generated content? | | **A** | Announcements & Live Regions | Are streaming outputs, status changes, and AI errors announced to assistive tech without spamming? | | **R** | Respect for User Preferences