agentleFS
Sign inStart free
aaziraniaazirani/flutter_agentify/.agents/skills/accessibility/SKILL.md

accessibility

Skill0 starsChanged 4 days agoMITView on GitHub

What a screen needs so everyone can use it, such as semantic labels on icon-only buttons, 48-point touch targets, contrast from theme roles, text scaling and focus order. Use when adding a button, icon, list row, dialog or form.

129 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use author-contributions, tool-rename-deprecation and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    author-contributions

    Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

    Also in 7 projects that use this

  • gitpod-ioSkill

    tool-rename-deprecation

    Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

    Also in 5 projects that use this

  • DepressionCenterSkill

    project-preferences

    Apply repository-specific preferences when planning, implementing, or reviewing changes in this project.

    Also in 6 projects that use this

  • MicrosoftSkill

    chat-perf

    Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

    Also in 5 projects that use this

  • DepressionCenterSkill

    create-media-pack

    Create a coordinated project branding and media pack with three accessible design options, approved vector artwork, image exports, a branding guide, and README integration. Use when asked for a repository media pack, brand kit, or complete project visual identity.

    Also in 5 projects that use this

  • +7 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 118 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Don't load this for translating text or mirrored layout.

    line 8
  2. Very specific:

    Every icon-only control has a label: tooltip: on IconButton, or a Semantics(label: ...) wrapper.

    line 12
  3. Very specific:

    No automated check exists for these.

    line 18
  4. Very specific:

    Look at lib/presentation/home/home_screen.dart: the app bar buttons carry tooltip: _tr('settings', 'Settings') and tooltip: …

    line 26
  5. Distinctive:

    No lint rule or doctor check.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 118 edited versions of this file we could read. “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

Accessibility

Don't load this for translating text or mirrored layout; see i18n-and-rtl.

Rule

  • Every icon-only control has a label: tooltip: on IconButton, or a Semantics(label: ...) wrapper. The label is a translated string.
  • Touch targets are at least 48 by 48 points.
  • Text and icon colors come from paired theme roles (onSurface on surface, onError on error), never a picked shade.
  • Text grows with the system text scale; nothing clips or overflows at 200 percent.
  • Focus order follows reading order, and a dialog puts focus on its first field.

No automated check exists for these. no_hardcoded_strings does cover tooltip and semanticLabel text, and no_hardcoded_colors blocks literal colors, which helps contrast indirectly. The rest is review plus a manual pass.

Why

Screen readers announce what has a label and skip what does not. Paired theme roles keep contrast correct in light and dark. People who raise the text size, or use a keyboard, need the same screen to work.

How

  • Look at lib/presentation/home/home_screen.dart: the app bar buttons carry tooltip: _tr('settings', 'Settings') and tooltip: _tr('clear_selection', ...); the floating action button has tooltip: _tr('add_item', ...). Copy that for every new IconButton.
  • IconButton and the Material buttons already give a 48-point target. If you build a tap area from GestureDetector or InkWell around a small icon, wrap it in ConstrainedBox(constraints: BoxConstraints(minWidth: 48, minHeight: 48)). The theme sets minimumSize for its buttons in lib/core/theme/app_theme.dart.
  • Contrast: use colorScheme.onX with X, as the delete background in lib/presentation/home/home_screen.dart does (error with onError). For secondary text use onSurfaceVariant, not a custom grey.
  • Text scale: use Theme.of(context).textTheme styles, allow wrapping (maxLines with ellipsis only where truncation is safe), and avoid fixed heights on rows that hold text. Put a long form in a scrollable.
<!-- @example:begin -->
  • Focus: keep widgets in reading order in the tree. Use autofocus: true on the first field of a dialog, as _ItemDialog does.
<!-- @example:end --><!-- @empty: - Focus: keep widgets in reading order in the tree. Use `autofocus: true` on the first field of a dialog, as `_ItemDialog` in .agents/example/lib/presentation/home/home_screen.dart does. -->
  • State must not rely on color alone: the selected row in lib/presentation/home/home_screen.dart also sets ListTile.selected.
<!-- @example:begin -->
  • Dismiss-to-delete gestures need a button path too; the row's delete goes through _confirmDelete and the same delete_item action.
<!-- @example:end --><!-- @empty: - Dismiss-to-delete gestures need a button path too; in the example, the row's delete goes through `_confirmDelete` (.agents/example/lib/presentation/home/home_screen.dart) and the same `delete_item` action. -->

Anti-patterns

  • IconButton(icon: Icon(Icons.add), onPressed: ...) with no tooltip.
  • A 24-point tappable icon with no padding.
  • Text(..., style: TextStyle(color: Colors.grey)).
  • SizedBox(height: 56) around a text row.
  • A gesture-only action (swipe, long press) with no visible control.
  • Error or success shown only as a color change.

Verification

  • No lint rule or doctor check. Check by hand: turn on a screen reader, set the system text size to the largest, tab through with a keyboard, switch to dark mode.
  • In a widget test, tester.getSemantics(find.byTooltip(...)) or find.byTooltip proves a label exists; see test/presentation/home/home_screen_test.dart for the harness.
  • tool/check.sh ends with All checks passed.

Related skills

  • ui-design — the five states and tokens.
  • i18n-and-rtl — keys for every label.

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.

Check your setup, free