Kb Mobile Accessibility logo

Kb Mobile Accessibility

Organization
Community-Access
kb-mobile-accessibility

Reference data, not a reviewer. Audit React Native, Expo, iOS, Android for accessibility. Review accessibilityLabel, accessibilityRole, accessibilityHint, touch targets (44x44pt min), screen reader support, and platform semantics.

Overview

PublisherCommunity-Access
Repositoryaccessibility-agents
Skill namekb-mobile-accessibility
Stars
429
Forks
51
Bundled files
1
LicenseMIT
Links
  • 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 Community-Access on GitHub. Read the source before you install it.

Installation

Install the Kb Mobile Accessibility 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/Community-Access/accessibility-agents/tree/main/skills/kb-mobile-accessibility
  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/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p .claude/skills
cp -r /tmp/accessibility-agents/skills/kb-mobile-accessibility .claude/skills/kb-mobile-accessibility
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Kb Mobile Accessibility 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 Kb Mobile Accessibility 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 Kb Mobile Accessibility 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.

Mobile Accessibility Skill

This skill provides mobile accessibility reference data for React Native, Expo, iOS, and Android auditing. Used by mobile-accessibility.agent.md.


React Native Accessibility Props - Full Reference

Each prop, with its type, values or notes, WCAG SC and required.

PropTypeValues / NotesWCAG SCRequired
accessiblebooleantrue marks the view as an accessibility node4.1.2Conditional
accessibilityLabelstringHuman-readable name - overrides all child text1.1.1, 4.1.2Yes (all interactive + image elements)
accessibilityLabelledBystring / string[]References ID(s) of labelling element1.3.1For form inputs
accessibilityRolestring (see roles table)Communicates element type to AT4.1.2Yes (all interactive elements)
accessibilityHintstringAdditional context spoken after label + role1.3.3When action isn't obvious
accessibilityStateobject{checked, disabled, expanded, selected, busy}4.1.2State-bearing elements
accessibilityValueobject{min, max, now, text}1.3.1Sliders, steppers, progress bars
accessibilityActionsarray[{name, label}] - defines custom actions4.1.3Context menus, long-press alternatives
onAccessibilityActionfunctionHandles custom action triggers4.1.3Paired with accessibilityActions
accessibilityLiveRegionstring'none' / 'polite' / 'assertive'4.1.3Dynamic content updates
accessibilityViewIsModalbooleantrue traps VoiceOver focus inside modal1.3.4Modals, drawers, sheets
accessibilityElementsHiddenbooleaniOS - hides element and children from VoiceOver1.1.1Decorative elements
importantForAccessibilitystringAndroid - 'auto' / 'yes' / 'no' / 'no-hide-descendants'1.1.1Decorative / grouped elements
accessibilityIgnoresInvertColorsbooleaniOS - preserves colors in Inverted Colors mode-Images, video
aria-labelstringRN 0.73+ alias for accessibilityLabel1.1.1, 4.1.2Preferred in new code
aria-labelledbystringRN 0.73+ alias for accessibilityLabelledBy1.3.1Form inputs
aria-describedbystringRN 0.73+ alias for accessibilityHint1.3.3Additional description
aria-rolestringRN 0.73+ alias for accessibilityRole4.1.2All interactive elements
aria-checkedboolean / 'mixed'RN 0.73+ alias for accessibilityState.checked4.1.2Checkboxes
aria-disabledbooleanRN 0.73+ alias for accessibilityState.disabled4.1.2Disabled elements
aria-expandedbooleanRN 0.73+ alias for accessibilityState.expanded4.1.2Accordions, dropdowns
aria-selectedbooleanRN 0.73+ alias for accessibilityState.selected4.1.2Tabs, list items
aria-busybooleanRN 0.73+ alias for accessibilityState.busy4.1.3Loading elements
aria-hiddenbooleanRN 0.73+ - maps to importantForAccessibility / accessibilityElementsHidden1.1.1Decorative content
aria-livestringRN 0.73+ alias for accessibilityLiveRegion4.1.3Dynamic content
aria-modalbooleanRN 0.73+ alias for accessibilityViewIsModal1.3.4Modals

Accessibility Role Values

Each role, with maps to (ios), maps to (android) and use for.

RoleMaps to (iOS)Maps to (Android)Use For
'button'UIAccessibilityTraitButtonAccessibilityNodeInfo.ROLE_BUTTONButtons, submission triggers
'link'UIAccessibilityTraitLinkAccessibilityNodeInfo.ROLE_LINKNavigation links, external URLs
'search'-ROLE_SEARCHSearch bars
'image'UIAccessibilityTraitImageROLE_IMAGEImages (when accessible=true)
'imagebutton'UIAccessibilityTraitImage+ButtonROLE_BUTTONIcon buttons
'header'UIAccessibilityTraitHeaderROLE_HEADINGHeadings
'text'UIAccessibilityTraitStaticTextROLE_LABELStatic text
'adjustable'UIAccessibilityTraitAdjustableROLE_SCROLL_VIEWSliders
'checkbox'-ROLE_CHECKBOXCheckboxes
'combobox'-ROLE_DROP_DOWN_LISTDropdowns
'menu'-ROLE_MENUMenus
'menuitem'-ROLE_MENU_ITEMMenu items
'menubar'-ROLE_MENU_BARMenu bars
'progressbar'UIAccessibilityTraitUpdatesFrequentlyROLE_PROGRESS_BARProgress indicators
'radio'-ROLE_RADIO_BUTTONRadio buttons
'radiogroup'--Radio button groups
'scrollbar'-ROLE_SCROLL_BARScrollbars
'spinbutton'-ROLE_SCROLL_VIEWSteppers, number inputs
'switch'-ROLE_SWITCHToggle switches
'tab'-ROLE_TABTab elements
'tablist'-ROLE_TAB_LISTTab containers
'timer'UIAccessibilityTraitUpdatesFrequently-Countdown timers
'toolbar'-ROLE_TOOL_BARToolbars
'grid'-ROLE_GRIDData grids
'list'-ROLE_LISTLists
'listitem'-ROLE_LIST_ITEMList items
'summary'UIAccessibilityTraitSummaryElement-Summary/status views
'alert'UIAccessibilityTraitCausesPageTurnROLE_ALERTAlert dialogs
'none'UIAccessibilityTraitNoneROLE_NONESuppress role

Touch Target Size Requirements

Each platform, with its minimum size, recommended and standard.

PlatformMinimum SizeRecommendedStandard
iOS44 x 44 pt44 x 44 ptHIG
Android48 x 48 dp48 x 48 dpMaterial Design
Web mobile44 x 44 CSS px (AAA)44 x 44 CSS pxWCAG 2.5.5
Web mobile (AA, 2.2)24 x 24 CSS px with spacing44 x 44 CSS pxWCAG 2.5.8

Detection Pattern (React Native)

tsx
// Violation: TouchableOpacity below minimum
const styles = StyleSheet.create({
  closeBtn: { width: 24, height: 24 },          // FAIL - below 44pt
  iconBtn: { width: 32, height: 32 },            // FAIL - below 44pt
  navBtn: { padding: 4 },                        // CONDITIONAL - depends on content size
  compliant: { width: 44, height: 44 },          // PASS
  compliantWithPadding: { padding: 12 },         // PASS if content >= 20pt
});

iOS UIAccessibility - Quick Reference

SwiftUI Modifiers

Each modifier, with its purpose.

ModifierPurpose
.accessibilityLabel("...")Overrides spoken name
.accessibilityHint("...")Spoken usage hint (after pause)
.accessibilityValue("...")Spoken current value
.accessibilityHidden(true)Removes from VoiceOver tree
.accessibilityElement(children: .combine)Merges child elements into one node
.accessibilityElement(children: .contain)Groups children as sub-elements
.accessibilityElement(children: .ignore)Container becomes accessible, children hidden
.accessibilityAddTraits(.isButton)Adds role trait
.accessibilityRemoveTraits(.isImage)Removes wrong role trait
.accessibilityInputLabels(["..."])Voice Control activation labels
.accessibilitySortPriority(n)Overrides VoiceOver reading order (higher = earlier)
.accessibilityAction(named: "...", {})Custom action in the Actions rotor
.accessibilityActivationPoint(CGPoint)Override activation tap point
.accessibilityCustomContent("label", "value")Extra info in Accessibility Inspector

SwiftUI Trait Values

isButton, isHeader, isLink, isImage, isStaticText, isSelected, isKeyboardKey, isSearchField, playsSound, isModal, updatesFrequently, startsMediaSession, allowsDirectInteraction, causesPageTurn, isTabBar, isSummaryElement

UIKit Properties

Each property, with its type and notes.

PropertyTypeNotes
isAccessibilityElementBoolSet true on custom views
accessibilityLabelString?Overrides spoken name
accessibilityHintString?Spoken after pause
accessibilityValueString?Current value (sliders, progress)
accessibilityTraitsUIAccessibilityTraitsBitfield of traits (.button, .header, etc.)
accessibilityFrameCGRectDetermines VoiceOver focus rect
accessibilityActivate()funcOverride activation behavior
accessibilityElements[Any]?Set container's VoiceOver child order
shouldGroupAccessibilityChildrenBoolGroups all children into single node
accessibilityViewIsModalBooltrue = VoiceOver trapped inside
accessibilityElementsHiddenBoolHides all children from VoiceOver

Android Jetpack Compose Semantics - Quick Reference

Each modifier / property, with its purpose.

Modifier / PropertyPurpose
semantics { contentDescription = "..." }Accessible name
semantics { role = Role.Button }Element role
semantics { stateDescription = "..." }Current state text
semantics { heading() }Marks as heading
semantics { selected = true/false }Selected state
semantics { toggleableState = ToggleableState.On }Toggle state
semantics { onClick(label = "...", action = {...}) }Click action with label
semantics { disabled() }Disabled state
semantics { focused = true }Force focus
semantics { liveRegion = LiveRegion.Polite }Live region announcements
semantics { invisibleToUser() }Hide from TalkBack
semantics { mergeDescendants = true }Merge child semantics into one node
clearAndSetSemantics { ... }Replace all descendant semantics
Modifier.semantics(mergeDescendants = true) { }Short merge pattern

Role Values

Role.Button, Role.Checkbox, Role.DropdownList, Role.Image, Role.RadioButton, Role.Switch, Role.Tab


Common Violation Patterns and Fixes

RN-001: Missing accessibilityLabel on icon button

tsx
// VIOLATION
<TouchableOpacity onPress={close}>
  <Icon name="x" size={20} />
</TouchableOpacity>

// FIX
<TouchableOpacity
  onPress={close}
  accessibilityRole="button"
  accessibilityLabel="Close"
>
  <Icon name="x" size={20} aria-hidden />
</TouchableOpacity>

RN-002: Image missing label

tsx
// VIOLATION
<Image source={productImage} style={styles.product} />

// FIX - informational image
<Image
  source={productImage}
  style={styles.product}
  accessibilityLabel="Blue suede shoes, size 10"
/>

// FIX - decorative image
<Image
  source={decorativeBackground}
  style={styles.bg}
  accessible={false}
  importantForAccessibility="no"
/>

RN-003: TextInput missing label

tsx
// VIOLATION - placeholder is not a label
<TextInput placeholder="Email" value={email} onChangeText={setEmail} />

// FIX
<View>
  <Text nativeID="emailLabel">Email address</Text>
  <TextInput
    value={email}
    onChangeText={setEmail}
    accessibilityLabelledBy="emailLabel"
    accessibilityHint="Enter your email address"
    keyboardType="email-address"
    autoComplete="email"
  />
</View>

RN-004: Checkbox missing state

tsx
// VIOLATION
<TouchableOpacity onPress={toggle}>
  <Image source={checked ? checkedIcon : uncheckedIcon} />
  <Text>Accept terms</Text>
</TouchableOpacity>

// FIX
<TouchableOpacity
  onPress={toggle}
  accessibilityRole="checkbox"
  accessibilityState={{ checked }}
  accessibilityLabel="Accept terms and conditions"
>
  <Image source={checked ? checkedIcon : uncheckedIcon} accessible={false} />
  <Text>Accept terms</Text>
</TouchableOpacity>

RN-005: Modal not trapping focus

tsx
// VIOLATION - custom modal without VoiceOver trap
<View style={styles.modal}>
  <Text>Are you sure?</Text>
  <Button title="Confirm" onPress={confirm} />
</View>

// FIX - use Modal component (traps focus automatically) or set accessibilityViewIsModal
<Modal
  visible={visible}
  transparent
  accessibilityViewIsModal={true}  // traps VoiceOver
  onRequestClose={close}           // Android back button
>
  <View style={styles.overlay}>
    <Text>Are you sure?</Text>
    <Button title="Confirm" onPress={confirm} />
    <Button title="Cancel" onPress={close} />
  </View>
</Modal>

AND-001: Compose image missing content description

kotlin
// VIOLATION
Image(
    painter = painterResource(id = R.drawable.product),
    contentDescription = null  // null = decorative, but wrong for informational image
)

// FIX - informational
Image(
    painter = painterResource(id = R.drawable.product),
    contentDescription = stringResource(R.string.product_image_description)
)

// FIX - truly decorative
Image(
    painter = painterResource(id = R.drawable.divider),
    contentDescription = null,
    modifier = Modifier.semantics { invisibleToUser() }
)

Testing Tool Commands

iOS Accessibility Inspector (Xcode)

text
Xcode -> Xcode menu -> Open Developer Tool -> Accessibility Inspector
- Run audit: Click "Audit" tab -> "Run Audit" button
- Inspect: "Inspection" tab -> hover over elements in Simulator
- Keyboard: Use +F7 to toggle VoiceOver in Simulator

Android Accessibility Scanner

bash
# Install (Play Store or adb)
adb install com.google.android.apps.accessibility.auditor

# Enable TalkBack via ADB (for CI)
adb shell settings put secure enabled_accessibility_services \
  com.google.android.marvin.talkback/.TalkBackService

# Check accessibility node tree
adb shell uiautomator dump /sdcard/ui_dump.xml
adb pull /sdcard/ui_dump.xml

React Native Testing Library

bash
npm install --save-dev @testing-library/react-native
tsx
import { render, screen, fireEvent } from '@testing-library/react-native';

test('button has accessible name and role', () => {
  render(<SubmitButton onPress={jest.fn()} />);
  const btn = screen.getByRole('button', { name: /submit/i });
  expect(btn).toBeTruthy();
});

test('checkbox updates state', () => {
  render(<TermsCheckbox />);
  const checkbox = screen.getByRole('checkbox', { name: /accept terms/i });
  expect(checkbox).toHaveAccessibilityState({ checked: false });
  fireEvent.press(checkbox);
  expect(checkbox).toHaveAccessibilityState({ checked: true });
});

Maestro (E2E)

yaml
# .maestro/accessibility-checks.yaml
appId: com.example.myapp
---
- launchApp
- assertVisible:
    label: "Submit form"
- tapOn:
    label: "Close"
- assertNotVisible:
    label: "Are you sure?"

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 Kb Mobile Accessibility AI skill do?

Reference data, not a reviewer. Audit React Native, Expo, iOS, Android for accessibility. Review accessibilityLabel, accessibilityRole, accessibilityHint, touch targets (44x44pt min), screen reader support, and platform semantics.

Why use Kb Mobile Accessibility on TypingMind?

Because you install it once and use it with any model. Kb Mobile Accessibility 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 Kb Mobile Accessibility in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-mobile-accessibility. 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 Kb Mobile Accessibility?

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 Kb Mobile Accessibility?

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

Is the Kb Mobile Accessibility AI skill free?

Yes. It is published on GitHub by Community-Access 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.

View all

Set up your own AI workspace now

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