skills.rest
lord-vinayak
lord-vinayakCOMMUNITY
Explore all skills by this author →
Website𝕏@lord_vinayak_GitHub

mobile-touch-auditor

Audit mobile UI accessibility against WCAG 2.2 AA/AAA criteria.

Updated May 19, 2026
Search Tags:#wcag 2.2#iOS#Android#voiceover#talkback#mobile accessibility
One-click install
npx skills add https://github.com/lord-vinayak/orive-reqcap --skill mobile-touch-auditor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-touch-auditor
Source: https://github.com/lord-vinayak/orive-reqcap/tree/main/.claude/skills/audit/mobile-touch-auditor_
Command: npx skills add https://github.com/lord-vinayak/orive-reqcap --skill mobile-touch-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires , and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The Mobile Touch Auditor skill unit helps identify accessibility issues in mobile applications, ensuring they are inclusive and accessible for all users.

Core Features & Use Cases

  • Audit mobile accessibility: Covers iOS, Android, web, wearables, and tablet UI with WCAG criteria.
  • Platform-specific checks: VoiceOver on iOS and TalkBack on Android are thoroughly tested.
  • Customizable scoring system: Rates touch targets, gestures, orientation, accessibility tools, virtual keyboards, and inputs on a scale from 0 to 10.

Quick Start

Audit a mobile application using the 'mobile-touch-auditor' skill, providing the necessary parameters like the application's name, target platform, and testing context.

Frequently Asked Questions about mobile-touch-auditor

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

FAQPage Schema
How do I audit mobile UI accessibility for WCAG 2.2 compliance?▼

Mobile UI accessibility audits evaluate touch targets, gestures, and screen reader compatibility against WCAG 2.2 AA/AAA criteria. This process identifies violations across iOS, Android, and tablet platforms to ensure inclusive applications.

What is the best way to test VoiceOver and TalkBack compatibility on mobile devices?▼

Testing VoiceOver on iOS and TalkBack on Android involves assessing screen reader navigation, virtual keyboards, and input handling. A thorough audit scores these interactions on a customizable scale to measure accessibility compliance accurately.

Does this mobile accessibility audit cover both smartphones and tablets?▼

Yes, mobile accessibility audits cover smartphones, tablets, and wearables. The evaluation assesses platform-specific criteria across iOS, Android, and web devices, ensuring orientation handling and touch targets meet WCAG 2.2 standards.

How do I check if my mobile touch targets meet accessibility standards?▼

Checking mobile touch targets involves measuring their size and spacing against WCAG 2.2 AA/AAA requirements. An auditor evaluates these elements alongside gestures and inputs, providing a 0 to 10 scoring system to rate compliance.

Why does my mobile app fail screen reader navigation tests?▼

Mobile apps fail screen reader tests due to unlabelled elements, poor focus management, or incompatible gestures. Auditing with VoiceOver or TalkBack identifies these specific violations and rates the virtual keyboard interactions for compliance.

Related Skills

Explore More Product & Management Skills→
Logos-LiberLogos-Liber
17

mobile-testing

Plan mobile app testing strategies for iOS and Android platforms.

Official
Intermediate
CrazyDubyaCrazyDubya

accessibility-auditor

Audit web applications for WCAG 2.1 Level AA accessibility compliance.

Community
Intermediate
Community-AccessCommunity-Access
387

Mobile Accessibility

Audit mobile app code for accessibility compliance across React Native, Expo, iOS, and Android.

Official
Advanced
James-GamboaJames-Gamboa

accessibility

Audit web content against WCAG 2.2 and Lighthouse accessibility criteria.

Community
Advanced