About

Imported from krutikjain/android-agent-skills (skills/android-compose-accessibility/SKILL.md). Install upstream with npx skills add krutikjain/android-agent-skills --skill android-compose-accessibility. Copyright stays with the author.

Android Compose Accessibility

Name: android-compose-accessibility
Author: krutikjain

When To Use

Use this skill when the request is about: compose accessibility review, android semantics issue compose, focus order in compose.
Primary outcome: Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets.
Handoff skills when the scope expands:
android-ui-states-validation
android-testing-ui

Workflow

Identify whether the target surface is Compose, View system, or a mixed interoperability screen.
Select the lowest-friction UI pattern that satisfies responsiveness, accessibility, and performance needs.
Build the UI around stable state, explicit side effects, and reusable design tokens.
Exercise edge cases such as long text, font scaling, RTL, and narrow devices in the fixture apps.
Validate with unit, UI, and screenshot-friendly checks before handing off.

Guardrails

Optimize for stable state and predictable rendering before adding animation or abstraction.
Respect accessibility semantics, contrast, focus order, and touch target guidance by default.
Do not mix Compose and View system ownership without an explicit interoperability boundary.
Prefer measured performance work over premature micro-optimizations.

Anti-Patterns

Embedding navigation or business logic directly in leaf UI components.
Using fixed dimensions that break on localization or dynamic text.
Ignoring semantics and announcing only visual changes.
Porting XML patterns directly into Compose without adapting the mental model.

Examples

Happy path

Scenario: Add semantics and readable labels to the Compose OrbitTasks cards.
Command: cd examples/orbittasks-compose && ./gradlew :app:connectedDebugAndroidTest

Edge case

Scenario: Validate font scaling, contrast, and touch targets in narrow layouts.
Command: cd examples/orbittasks-compose && ./gradlew :app:assembleDebug

Failure recovery

Scenario: Differentiate accessibility requests from general UI validation or theme work.
Command: python3 scripts/eval_triggers.py --skill android-compose-accessibility

Done Checklist

The implementation path is explicit, minimal, and tied to the right Android surface.
Relevant example commands and benchmark prompts have been exercised or updated.
Handoffs to adjacent skills are documented when the request crosses boundaries.
Official references cover the chosen pattern and the main migration or troubleshooting path.

Official References

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/krutikjain-android-agent-skills-android-compose-accessibility/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

krutikjain-android-agent-skills-android-compose-accessibility.ocm.jsonjson

{
  "ocm": "1",
  "id": "krutikjain-android-agent-skills-android-compose-accessibility",
  "kind": "skill",
  "name": "android-compose-accessibility",
  "description": "Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets.",
  "publisher": "krutikjain",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "android",
      "compose",
      "accessibility",
      "a11y",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/krutikjain/android-agent-skills",
      "path": "skills/android-compose-accessibility/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/krutikjain/android-agent-skills/blob/HEAD/skills/android-compose-accessibility/SKILL.md",
      "key": "krutikjain/android-agent-skills/skills/android-compose-accessibility/SKILL.md"
    }
  },
  "instructions": "# Android Compose Accessibility\n\n## When To Use\n- Use this skill when the request is about: compose accessibility review, android semantics issue compose, focus order in compose.\n- Primary outcome: Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets.\n- Handoff skills when the scope expands:\n- `android-ui-states-validation`\n- `android-testing-ui`\n\n## Workflow\n1. Identify whether the target surface is Compose, View system, or a mixed interoperability screen.\n2. Select the lowest-friction UI pattern that satisfies responsiveness, acc",
  "cost": {
    "context_tokens": 766
  }
}

Fetch it by URL: GET /api/v1/registry/krutikjain-android-agent-skills-android-compose-accessibility/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.