agentsclimarketplace

Mobile accessibility

Skill ahtishamshahzad/agent_dev_flow/.ai/skills/mobile/mobile-accessibility

Tool-neutral AI Engineering System: 174 reusable skills (installable as Claude Code plugins) for planning and building software with AI agents. Classify → plan → approve → build under quality gates. Works with Claude Code, Codex, Cursor, Windsurf, Copilot & Antigravity. Canonical in .ai/.

Install
npx -y skills add ahtishamshahzad/agent_dev_flow --skill mobile-accessibility

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 21 days oldThe repository was created 21 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.
  • 0 stars0 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

Use to plan mobile accessibility — screen-reader labels/roles, focus order, touch target sizes, contrast, and dynamic type — so the app is usable with assistive tech. Bakes accessibility into components, not bolts it on.

SKILL.md

3.2 KB, as published. Nobody here has run it

Mobile Accessibility

Purpose

Plan accessibility: screen-reader support (labels/roles/state), focus order, adequate touch targets, sufficient contrast, and dynamic type — built into components.

When to Use

  • Whenever building UI, especially interactive components and forms.
  • Never skip for 'later' — build it in.

Inputs

  • The UI/components and their interactions.
  • Design tokens (contrast/sizing) and platform a11y APIs.

Discovery Questions

  • What assistive-tech support is required (VoiceOver/TalkBack)?
  • Are touch targets and contrast within guidelines?
  • Does the app support dynamic type/large text?
  • What is the focus order for key flows?

Responsibilities

  • Add accessibility labels/roles/state to interactive elements.
  • Ensure focus order and screen-reader flow.
  • Meet touch-target size and contrast minimums (mobile-design-system).
  • Support dynamic type/large text; avoid text truncation that breaks meaning.

Required Workflow

  1. Review components/flows for a11y.
  2. Add labels/roles/state + focus order.
  3. Verify target sizes + contrast against tokens.
  4. Support dynamic type.
  5. Record the a11y plan; test with a screen reader.

Decision Rules

  • Accessibility is built into components, not bolted on later.
  • Meet platform target-size and contrast minimums.
  • Support dynamic type; don't hard-lock font sizes.
  • Test key flows with a screen reader (or flag as unverified).

Rules

  • Interactive elements have labels/roles/state.
  • Meet contrast/target-size minimums.
  • Coordinate with design system and theme.

Anti-Patterns

  • Deferring accessibility indefinitely.
  • Icon-only buttons with no labels.
  • Tiny touch targets / low contrast.
  • Hard-locked font sizes ignoring dynamic type.

Validation Checklist

  • Labels/roles/state on interactive elements.
  • Focus order defined for key flows.
  • Target sizes + contrast meet minimums.
  • Dynamic type supported.
  • Tested with a screen reader (or flagged).

Definition of Done

A recorded accessibility plan and applied practices: labeled/role-tagged interactive elements, sensible focus order, compliant targets/contrast, and dynamic-type support — verified with a screen reader or explicitly flagged.

Related Skills

mobile-design-system, mobile-theme, mobile-fonts, mobile-component-testing

Related Knowledge

../../../knowledge/ (a11y requirements).

Related References

../../../references/mobile/screens/ when populated.

Context Loading Guidance

  • Requires: the UI/components + interactions, design tokens, a11y APIs.
  • Does not require: unrelated screens, the full mobile skill set, unrelated references.
  • May load: mobile-design-system, mobile-component-testing.
  • Stop when: the a11y plan is applied/verified (or flagged).

Token Efficiency Guidance

Focus on the interactive components in scope; reuse design tokens for contrast/sizing.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.