What problem does it solve? Flutter ships zero accessibility lint rules, so screen-reader support, text scaling, contrast, and tap-target correctness are silently broken unless authored into every widget by hand. This Skill turns accessibility into a coding standard enforced at authoring time and in review, rather than a backlog ticket. ## Core Features & Use Cases - Semantics authoring rules: Every interactive node gets Semantics(button: true, label), every Icon/Image gets a semanticLabel or ExcludeSemantics, and traversal order is set with OrdinalSortKey instead of layout position. - Text-scale and state discipline: Bans MediaQuery.withClampedTextScaling, textScaleFactor, FittedBox, and ellipsis on labels; requires reading boldText/disableAnimations from MediaQuery and encoding state through non-color channels. - Contrast and target verification: Enforces 4.5:1 body / 3:1 large-text contrast against composited backgrounds in both themes, plus 44x44 single-tap targets. - Use Case: When adding a GestureDetector or Icon to a Flutter View, apply the wrong/right ItemTile patterns and the definition-of-done checklist so TalkBack, VoiceOver, and Switch Access work without a retrofit. ## Quick Start Review this Flutter widget diff and rewrite any tap targets, icons, or text that violate the accessibility-as-code rules.
