Individual skill
flutter-accessibility
Use when implementing or auditing accessibility on a Flutter screen — the Semantics widget, screen-reader labels (TalkBack/VoiceOver), colour contrast, minimum tap-target size, system font scaling, or semantics in a web build. Also triggers on "make this accessible", "a11y", or a request for an accessibility review.
skills/flutter-accessibility/SKILL.md
Source commit addd6d85e5d92bacc1e8bf14c23c585380a4b371
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 14
- Repository last updated
- Oct 30, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-coding-assistant Repository topic
- claude-code Repository topic
- clean-architecture Repository topic
- dart Repository topic
- flutter Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
You are implementing or auditing accessibility (a11y) for a Flutter app.
## Context
Accessibility pressure differs by surface, and it changes what you prioritise:
- **Customer-facing web** — the highest bar. Screen-reader semantics are off by
default on Flutter web (see section 5), the audience is unknown, and in many
jurisdictions this is a legal requirement, not a nicety.
- **Internal/admin web** — keyboard navigation and contrast matter most; staff
use these all day.
- **Mobile** — platform screen readers (TalkBack/VoiceOver) mostly work if you
give widgets labels and keep tap targets large enough.
