Flutter accessibility
Skill musabekisakov-imj/flutter-design-engineer/skills/flutter-accessibility
Agent skills for product-aware, adaptive, accessible, and visually verified Flutter UI design engineering
npx -y skills add musabekisakov-imj/flutter-design-engineer --skill flutter-accessibilityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Audit and improve Flutter accessibility, inclusive interaction, localization safety, and RTL behavior. Use for screen-reader semantics, focus and keyboard navigation, text scaling, contrast, touch targets, reduced motion, form errors, RTL, localization, or accessibility acceptance checks.
SKILL.md
2.0 KB, as published. Nobody here has run it
Flutter Accessibility
Treat accessibility failures that block core tasks as release blockers.
Audit
- Identify core journeys and the assistive modes relevant to supported platforms.
- Inspect semantics, labels, values, hints, grouping, headings, live updates, and decorative exclusions.
- Traverse with keyboard, switch-like focus, and screen reader where available.
- Test system text scaling up to the supported maximum without clipping or hiding critical actions.
- Verify contrast, non-color cues, touch targets, error association, disabled-state clarity, and motion preferences.
- Test long translations, pluralization, bidirectional content, mirrored navigation, and directional icon correctness.
- Read
references/accessibility-and-localization.mdand relevant platform guidance already present in the project. For multi-domain dashboards, readreferences/connected-product-workflows.mdand align semantic order with cross-domain visual priority.
Implement
- Prefer semantic native Flutter controls before custom gesture surfaces.
- Merge or exclude semantics intentionally; do not create duplicate announcements.
- Keep focus order aligned with visual and task order.
- Announce asynchronous errors and important state changes without excessive chatter.
- Use logical direction APIs (
start/end) when layout should mirror. - Do not disable text scaling to protect a fragile layout.
- Provide reduced-motion behavior without removing necessary feedback.
Verify and Report
State tools, platforms, text scales, locales, directions, themes, and journeys tested. Distinguish automated checks from manual assistive-technology verification and identify gaps.