skills.rest
cbemister
cbemisterCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

mobile-accessibility

Audit mobile apps for VoiceOver and TalkBack accessibility gaps.

Updated Feb 4, 2026
Search Tags:#accessibility#mobile#wcag#voiceover#focus-management#talkback
One-click install
npx skills add https://github.com/cbemister/claude-code-utils --skill mobile-accessibility
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-accessibility
Source: https://github.com/cbemister/claude-code-utils/tree/main/.claude/skills/mobile-accessibility
Command: npx skills add https://github.com/cbemister/claude-code-utils --skill mobile-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mobile apps often fail accessibility checks, leaving users with visual, motor, and cognitive barriers. This skill provides a comprehensive framework to audit, implement, and validate VoiceOver (iOS), TalkBack (Android), and screen reader navigation, ensuring keyboard focus and dynamic content are usable.

Core Features & Use Cases

  • Audit touch target sizes, focus order, ARIA landmarks, and live regions aligned with WCAG 2.1 mobile criteria.
  • Implement screen reader announcements for dynamic content and ensure proper labels, roles, and hints.
  • Validate modal and bottom-sheet focus trapping and accessible dismissal across iOS and Android.
  • Provide automated quick-start checks and manual testing guidance for developers and QA.

Quick Start

Audit the mobile UI for accessibility gaps and apply VoiceOver and TalkBack improvements, focusing on focus management and screen reader announcements.

Frequently Asked Questions about mobile-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit mobile app accessibility for VoiceOver and TalkBack compatibility?▼

Audit mobile app accessibility by validating touch target sizes, focus order, ARIA landmarks, live regions, and dynamic content announcements against WCAG 2.1 mobile criteria. Apply automated quick-start checks alongside manual testing guidance for iOS and Android screen reader navigation.

What WCAG 2.1 mobile accessibility criteria should my app satisfy?▼

WCAG 2.1 mobile accessibility criteria require sufficient touch target sizes, proper focus management, screen reader announcements for dynamic content, support for orientation changes, and respect for motion preferences. Validate modal and bottom-sheet focus trapping and accessible dismissal across iOS and Android to ensure full compliance.

How do I manage focus trapping in mobile modals and bottom sheets?▼

Manage focus trapping in mobile modals and bottom sheets by validating accessible dismissal and ensuring proper focus order for VoiceOver and TalkBack navigation. Apply actionable heuristics to trap keyboard and screen reader focus within the active modal until it is explicitly dismissed.

Does this mobile accessibility audit work for both iOS and Android?▼

Yes, this mobile accessibility audit works for both iOS and Android. It validates VoiceOver and TalkBack compatibility, applying WCAG 2.1 mobile criteria to audit touch targets, focus management, ARIA landmarks, and dynamic content announcements across both platforms.

How do I implement screen reader announcements for dynamic content?▼

Implement screen reader announcements for dynamic content by applying proper labels, roles, and hints, and configuring live regions. Validate that VoiceOver and TalkBack correctly announce content updates and dynamic changes without interrupting the user's current focus order.

Why does my mobile UI fail accessibility checks on orientation changes?▼

Mobile UI accessibility checks fail on orientation changes when focus management is lost or content is not properly announced during the layout transition. Validate orientation support and motion preferences to ensure screen reader focus is maintained and dynamic content updates are correctly announced.

Related Skills

Explore More Software Engineering Skills→
marcusagmmarcusagm
4

mobile-games

Define platform-constrained design and performance guidelines for iOS and Android mobile games.

Community
Basic
emilneuraz-aiemilneuraz-ai

screen-reader-testing

Validate web accessibility by testing applications with screen readers.

Community
Advanced
krzemienskikrzemienski
2

responsive-validation

Validate responsive UI layouts across device viewports and breakpoints.

Community
Advanced
mrodrigues1mrodrigues1

accessibility-compliance

Implement WCAG 2.2 compliant accessibility patterns and remediation guidance for web and mobile interfaces.

Community
Intermediate