What problem does it solve? Flutter apps often ship with accessibility barriers—missing semantic labels, undersized touch targets, keyboard-inaccessible controls, and animations that ignore reduced-motion settings—because WCAG 2.2 compliance is hard to verify manually across iOS, Android, Web, macOS, Windows, and Linux. ## Core Features & Use Cases - Structured WCAG 2.2 Audits: Runs a four-phase workflow that captures the target conformance level (A, AA, AA + selected AAA, or AAA) and target platforms, then audits widgets across seven categories including semantics, touch targets, focus, contrast, text scaling, motion, and forms. - Actionable Findings with Fixes: Every finding cites the exact WCAG criterion ID and name, a CRITICAL/MAJOR/MINOR severity, and before-and-after Dart code, with per-platform severity adjustments. - Remediation with Regression Tests: Applies user-selected fixes and generates accessibility tests covering semantics, target sizes, focus management, and disableAnimations gating so fixes cannot regress. - Use Case: Point the skill at a checkout screen and receive a full audit report flagging a 16x16 GestureDetector close button as CRITICAL under WCAG 2.1.1, then have it replaced with a compliant IconButton and locked in with a widget test. ## Quick Start Ask the assistant to audit your Flutter widget files for WCAG 2.2 accessibility and specify your target conformance level and platforms when prompted.
