WebInclusiveby Giuseppe Stumbo

Assessing native apps

App users move between screens, controls and system settings. This guide helps you choose Android and iOS journeys to test and document native components, interface adaptation and hybrid transitions. Dedicated guides cover TalkBack and VoiceOver.

Define the scope and test matrix

A reliable assessment declares journeys, builds, devices and configurations. The sample must represent actual use, not every available model.

  1. Start with critical journeys, not individual screens

    Define the tasks a person needs to complete and include alternative states that may interrupt the journey.

    • Sign-in, registration, account recovery and consent.
    • Search, purchase, payment or another primary product task.
    • Errors, system permissions, notifications, deep links and expired sessions.

  2. Choose representative combinations

    The matrix must specify platform, system version, device model and app build: “tested on mobile” is not enough.

    • A current version and a still-supported version for each platform.
    • Different screens and densities where they actually change the layout.
    • Relevant orientation, text size and accessibility settings.

  3. Separate native, WebView and hybrid content

    Note where the technology changes: native components and embedded web content expose different semantics and behaviours.

    • Identify transitions between the app, browser, WebView and system screens.
    • Check that focus is not lost during a context change.
    • Keep the same test scenario across environments.

Assess native interface behaviour

First check the app's structure and adaptation; screen reader testing complements the assessment but does not replace other checks.

  • Semantics

    Name, role, state and navigation order

    Check what the platform exposes for buttons, fields, custom controls, messages and changing content.

    • Understandable labels that do not depend on visual position.
    • Up-to-date selected, expanded, disabled and error states.
    • Focus order consistent with the task and the screen's reading order.

  • Adaptation

    Large text, orientation and reflow

    Increase text size in system settings and check that content and actions remain legible and usable.

    • No truncated, overlapping or hidden text without an alternative.
    • Essential actions remain available when the layout reflows.
    • Orientation locked only where genuinely necessary.

  • Interaction

    Touch, gestures and custom components

    Check target size and spacing, alternatives to complex gestures and consistent responses from custom controls.

    • Targets reachable without accidental activation.
    • A simple alternative to dragging and multipoint gestures.
    • Perceivable feedback after submission, loading, errors and completion.

Continue with the platform guide

Once you have prepared the app journey, open the TalkBack or VoiceOver guide to run tests with the platform's screen reader.

  • Android

    Complete the assessment with TalkBack

    After the general checks, use the Android guide for touch exploration, swiping, granularity, large text and evidence collection.

  • iOS

    Complete the assessment with VoiceOver

    Use the iOS guide to assess navigation order, rotor, announcements, Dynamic Type and focus management.

Document the defect and verify the fix

A useful report allows development and QA to reproduce the issue and verify the fix under the same test conditions.

  1. Make every issue reproducible

    For each defect, record the context needed to repeat the test without interpretation.

    • App build, device, operating system and active settings.
    • Steps, expected result, observed result and impact on the journey.
    • Screenshots or recordings only when they clarify behaviour.

  2. Repeat the scenario, not just the fixed point

    Retesting verifies that a defect has been resolved; regression testing checks the effects of changes on the complete journey and affected platforms.

    • Verify the fix using the same device, operating system and assistive technology used to find the issue.
    • Repeat the steps before and after the modified point.
    • Update status and evidence without deleting the history.