About flutter-accessibility
flutter-accessibility is a skill for auditing and implementing accessibility in Flutter projects. It covers assistive navigation, text scaling, contrast, localization, and motion, then asks for a report distinguishing automated checks from manual verification.
Key features
- 01Audit semantics and assistive navigation
- 02Test text scaling and contrast
- 03Check localization and RTL layouts
- 04Prefer native semantic controls
- 05Report verification and gaps
Use cases
- 01Review a Flutter app before release
- 02Check keyboard and screen-reader journeys
- 03Test translated and bidirectional interfaces
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/flutter-accessibilityin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlreferences/accessibility-and-localization.mdconnected-product-workflows.mdDetails
From the project READMEFlutter 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.
Comments
Markdown supported