TypingMindTypingMindThe best frontend for AI
Accessibility Audit Android logo

Accessibility Audit Android

Community
khadinakbarlabs
accessibility-audit-android

Run Android accessibility audit: TalkBack, contrast, touch targets, content descriptions. Use when the user says 'a11y audit android', 'accessibility android', 'talkback', 'screen reader android'.

Overview

Publisherkhadinakbarlabs
Repositoryexpo-mobile-app-builder
Skill nameaccessibility-audit-android
Stars
3
Forks
0
Bundled files
1
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by khadinakbarlabs on GitHub. Read the source before you install it.

Installation

Install the Accessibility Audit Android AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/accessibility-audit-android
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/khadinakbarlabs/expo-mobile-app-builder.git /tmp/expo-mobile-app-builder
mkdir -p .claude/skills
cp -r /tmp/expo-mobile-app-builder/skills/accessibility-audit-android .claude/skills/accessibility-audit-android
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Accessibility Audit Android in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Accessibility Audit Android on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Accessibility Audit Android is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Accessibility Audit (Android)

Pre-launch a11y check. Google rewards accessible apps with featuring.

The WCAG 2.1 AA baseline

  • Color contrast 4.5:1 (text), 3:1 (large text + icons)
  • Touch targets 48×48 dp minimum
  • All actionable elements have content description
  • Focus order matches visual order
  • No critical info conveyed by color alone

Test with TalkBack

Enable: Settings → Accessibility → TalkBack → ON.

Navigation:

  • Swipe right → next element
  • Swipe left → previous
  • Double-tap → activate
  • 2-finger swipe → scroll
  • 3-finger swipe → next/prev page

Walk every screen of your app. Listen to what TalkBack reads.

Common TalkBack failures

  • Image with no accessibilityLabel → reads "image"
  • Custom buttons without role → reads as static text
  • Status changes not announced → users miss updates

RN+Expo accessibility props

tsx
<Pressable
  accessibilityLabel="Save habit"
  accessibilityHint="Saves your current habit"
  accessibilityRole="button"
  accessibilityState={{ disabled: !canSave }}
  onPress={save}
>
  <Text>Save</Text>
</Pressable>
PropUse
accessibilityLabelWhat this element is ("Save button")
accessibilityHintWhat happens on action ("Saves your habit")
accessibilityRoleType: button, link, header, image, etc
accessibilityStateDisabled, selected, expanded
accessibilityValueFor sliders, etc.
accessibleGroup children as single focus element
importantForAccessibility"yes" / "no-hide-descendants"

Touch targets

Minimum 48×48 dp. For visually smaller buttons, add hit slop:

tsx
<Pressable hitSlop={{ top: 10, bottom: 10, left: 10, right: 10 }}>

Color contrast

Use these tools:

  • accessible-colors.com — pick palette with contrast guarantees
  • webaim.org/resources/contrastchecker/
  • Material Color Tool — built-in contrast checker

Test with Accessibility Scanner (Android)

Install "Accessibility Scanner" from Play Store. Open your app, tap scan button → it audits visible screens and flags issues.

Common Android a11y gotchas

  • Custom switches without state → just say "checkbox unchecked" not "switch on"
  • Icons-only buttons missing label
  • Image inside button → use single accessibilityLabel on button, mark image importantForAccessibility="no"
  • Auto-focusing text fields breaks TalkBack flow
  • Modal dialogs trap focus → use accessibilityViewIsModal (Android only)

Pair with

  • apply-material3 (M3 has good a11y defaults)
  • accessibility-audit (cross-platform shared)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Accessibility Audit Android AI skill do?

Run Android accessibility audit: TalkBack, contrast, touch targets, content descriptions. Use when the user says 'a11y audit android', 'accessibility android', 'talkback', 'screen reader android'.

Why use Accessibility Audit Android on TypingMind?

Because you install it once and use it with any model. Accessibility Audit Android is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Accessibility Audit Android in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/accessibility-audit-android. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Accessibility Audit Android?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Accessibility Audit Android?

As many as you like. As long as a model supports skills, you can use Accessibility Audit Android with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Accessibility Audit Android AI skill free?

Yes. It is published on GitHub by khadinakbarlabs under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
NousResearch logo

Antigravity Cli

NousResearch
OrganizationPopular

Operate the Antigravity CLI (agy): plugins, auth, sandbox.

53.5K
250.4K
1 files
View
langgenius logo

Backend Code Review

langgenius
OrganizationPopular

Use only when the user explicitly requests a review or audit of backend code under `api/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests,…

24.9K
157.6K
4 files
View
langgenius logo

Frontend Code Review

langgenius
OrganizationPopular

Use only when the user explicitly requests a review or audit of frontend code under `web/` or `packages/dify-ui/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for…

24.9K
157.6K
8 files
View
anthropics logo

Command Development

anthropics
OrganizationPopular

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create…

23.8K
146.3K
9 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇