Skip to main content
    Mobile

    Mobile App Accessibility in India

    India is mobile-first, but most apps fail basic accessibility checks. What GIGW 3.0 and WCAG ask for, and how TalkBack and VoiceOver testing finds the gaps.

    Smartphone displaying an Android app with TalkBack screen reader enabled, showing the green focus rectangle highlighting a labelled navigation button and the spoken announcement overlay

    India is a mobile-first country. For hundreds of millions of people, a smartphone is the main way, and often the only way, to get online. Banking, e-commerce, government services, healthcare and entertainment all reach users through mobile first. Yet mobile app accessibility gets a fraction of the attention that web accessibility does. That is a compliance risk, and it also means a lot of missed customers.

    Why mobile is harder to test

    Mobile needs a different toolkit from the web. Web testing relies on browser tools and keyboard navigation. Mobile testing needs native screen readers (TalkBack on Android, VoiceOver on iOS), gesture navigation and device settings such as font scaling and display inversion. Most development teams have none of this set up.

    WCAG's mobile-relevant requirements cover touch target size (a minimum of 24x24px), pointer gestures (no action that needs a complex gesture without a simple alternative) and orientation (content should not lock to portrait or landscape unless it has to). Production apps break these often.

    What GIGW 3.0 signals

    India's updated GIGW 3.0 (May 2026) extends its scope to mobile apps, and government bodies are now expected to make their apps WCAG 2.1 AA compliant. Private-sector expectations will likely follow as regulation matures. For BFSI companies, whose apps often get more use than their websites, this is particularly urgent.

    React Native and Flutter

    Many Indian app teams build in cross-platform frameworks such as React Native and Flutter. Both have improved their accessibility support, but the defaults are often wrong. React Native's accessibility props (accessibilityLabel, accessibilityRole, accessibilityHint) are frequently left out, and Flutter's Semantics widget has to be used on purpose. Without accessibility-aware development habits, cross-platform apps often end up broken for screen reader users.

    Where to start

    Turn on TalkBack (Android) and VoiceOver (iOS) and try to complete every core user journey using only the screen reader. The worst problems show up quickly: buttons with no labels, images with no descriptions, modals that trap focus, forms that announce nothing useful. Fix those first, then bring in a qualified auditor for a structured WCAG audit of the app.

    Back to all posts