Mobile App Accessibility: The Compliance Gap Indian Businesses Are Ignoring

India is a mobile-first country. For hundreds of millions of users, the smartphone is their primary — and often only — internet access point. BFSI apps, e-commerce platforms, government services, healthcare portals, and entertainment products are all delivered first through mobile. Yet mobile app accessibility receives a fraction of the attention that web accessibility does. This gap is both a compliance risk and a massive missed opportunity.

Why Mobile Accessibility Is Harder

Mobile accessibility testing requires a different toolkit than web. Where web testing uses browser-based tools and keyboard navigation, mobile testing requires native screen readers (TalkBack on Android, VoiceOver on iOS), gesture-based navigation, and device-specific settings like font scaling and display inversion. Most development teams do not have this testing infrastructure in place.

The WCAG mobile criteria address touch target size (minimum 24×24px), pointer gestures (no action requiring a complex gesture without a simple alternative), and orientation (content shouldn't lock to portrait or landscape unless essential). These are frequently violated in production apps.

The GIGW 3.0 Signal

India's updated GIGW 3.0 (May 2026) explicitly expanded its scope to cover mobile apps. Government bodies are now formally required to make their apps WCAG 2.1 AA compliant. The expectation will follow into the private sector as the regulatory environment matures. For BFSI companies, whose apps are arguably more used than their websites, this is particularly urgent.

India went mobile-first in access but not in accessibility. That's the gap to close.

The React Native and Flutter Problem

Many Indian app development teams work in cross-platform frameworks like React Native and Flutter. Both have made significant progress on accessibility support, but the defaults are often wrong. React Native's accessibility props (accessibilityLabel, accessibilityRole, accessibilityHint) are frequently omitted. Flutter's Semantics widget requires deliberate use. Without accessibility-aware development practices, cross-platform apps often produce screen-reader-broken interfaces.

Where to Start

Run your app through TalkBack (Android) and VoiceOver (iOS). Navigate every core user journey using only the screen reader. You will immediately identify the most severe failures: buttons with no labels, images with no descriptions, modals that trap focus, forms that announce nothing useful. These are your priority fixes. From there, engage a qualified auditor for a structured WCAG mobile audit.