agentleFS
thienqothienqo/flutter-skills/skills/flutter-accessibility/SKILL.md

flutter-accessibility

Skill16 starsChanged 2 months agoBSD-3-ClauseView on GitHub

Build or audit Flutter accessibility for semantics, screen readers, focus, keyboard access, text scaling, contrast, target size, and motion preferences. Pair with flutter-responsive-layout when large text causes reflow, clipping, or overflow across constraints.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat accessibility as behavior to implement and verify, not a label-only cleanup.

    line 8
  2. Very specific:

    Prefer semantic built-in controls before manually adding Semantics.

    line 16
  3. Distinctive:

    Keep visual, semantic, and keyboard focus order aligned.

    line 18
  4. Distinctive:

    Use widget tests with semantics enabled and Flutter's accessibility guideline matchers where suitable.

    line 27
  5. Distinctive:

    Read semantics and screen readers when annotating custom widgets with Semantics, merging subtrees, or triggering dynamic voice …

    line 31
  6. Distinctive:

    Read target sizes and contrast when auditing WCAG AA contrast ratios, minimum touch targets, or large text scaling adaptation.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Flutter Accessibility

Treat accessibility as behavior to implement and verify, not a label-only cleanup.

Audit the flow

Identify the primary task, semantic reading order, actionable controls, dynamic announcements, focus transitions, text scaling, contrast, motion, and keyboard or switch access on each target platform.

Rules

  • Prefer semantic built-in controls before manually adding Semantics.
  • Give custom interactive widgets roles, labels, values, states, and actions without duplicating child semantics.
  • Keep visual, semantic, and keyboard focus order aligned.
  • Allow text to scale without clipping or hiding essential actions.
  • Meet platform-appropriate target sizes and do not rely on color alone.
  • Preserve functionality with reduced motion and increased contrast preferences.
  • Announce meaningful asynchronous state changes without creating repetitive noise.
  • Exclude decorative content from the semantics tree when it adds no information.

Verification

Use widget tests with semantics enabled and Flutter's accessibility guideline matchers where suitable. Also test the changed flow with TalkBack or VoiceOver and keyboard navigation on supported desktop/web targets.

References

  • Read semantics and screen readers when annotating custom widgets with Semantics, merging subtrees, or triggering dynamic voice announcements.
  • Read target sizes and contrast when auditing WCAG AA contrast ratios, minimum touch targets, or large text scaling adaptation.

Sources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.