Skip to main content

Application

Find application requirements for testing mobile experiences.

Vision support (APP-1)

Custom display & text settings (APP-1-1)

Text content adapts to Larger Text setting.

How to test

Tool: Visual inspection

  1. Adjust OS level settings for Larger Text:
    • iOS: Settings > Accessibility > Display & Text Size > Larger Text On. Set the size to the third notch from the largest accessibility size (notch 8 of 11).
    • Android: Settings > Display > Font Size and Style > maximum setting.
  2. Confirm that all text content adapts when applied.

Test outcomes

  • Pass: All text content adapts to larger text setting when applied.

  • Fail: Some or all text content does not adapt to larger text setting when applied.

Related WCAG criteria

WCAG 2.2 AA - 1.4.4 Resize Textsize Text

Support screen reader (APP-1-2)

VoiceOver/TalkBack can be used to successfully interact with the full app experience

How to test

Tool: VoiceOver (iOS), TalkBack (Android)

  1. Interact with the full app experience and task flows using VoiceOver/TalkBack.
  2. Confirm that all functionality can be used easily and effectively by the screen reader.

Test outcomes

  • Pass: All features and functionality can be easily and successfully used with VoiceOver/TalkBack.

  • Fail: Some features and functionality cannot be easily and successfully used with VoiceOver/TalkBack.

Related WCAG criteria

502.2.2 No Disruption of Accessibility Features

View titled (APP-1-3)

Each screen/view needs to be titled and the title needs to be an accurate and descriptive title for the content presented on that screen/view.

How to test

Tool: VoiceOver (iOS), TalkBack (Android)

  1. Navigate to each view using the screen reader.
  2. Confirm that each view has a title read aloud by VoiceOver/TalkBack.

Test outcomes

  • Pass: All views have a title that will be read by VoiceOver or TalkBack.

  • Fail: One or more views are not titled.

Related WCAG criteria

WCAG 2.2 A - 2.4.2 Page Titled

Physical and motor support (APP-2)

Flexible orientation (APP-2-1)

Content is not restricted to one orientation, unless that orientation is essential, to allow users to orient the device according to their needs and personal setup.

How to test

Tool: Visual inspection

  1. Enable setting to allow orientation to switch based on how the device is oriented.
  2. Open the application being tested and confirm that each screen adapts to the portrait or landscape orientation change when the device is rotated between these orientations.

Test outcomes

  • Pass: All content adapts to current orientation as expected.

  • Fail: Some content that does not fall under the exception criteria in assumptions does not adapt to the current orientation as expected.

  • NA: The full app experience falls under the exception criteria in assumptions.

Related WCAG criteria

WCAG 2.2 AA - 1.3.4 Orientation

Motion control (APP-2-2)

When device motion is used to control the interface there is a way to deactivate it and operate the same functionality through UI controls instead

How to test

Tool: Visual inspection

  1. Determine whether device motion is used to control the interface.
  2. If device motion is used to control the interface, confirm that there is a way to deactivate motion control and operate the same functionality through UI controls instead.

Test outcomes

  • Pass: Motion input is used but it can be deactivated and an alternative is provided.

  • Fail: Motion input is used and cannot be disabled or an alternative to motion is not provided.

  • NA: Motion input is not used to control the interface.

Related WCAG criteria

WCAG 2.2 A - 2.5.4 Motion Actuation

Multiple authentication methods (APP-2-3)

User authentication must avoid relying on a cognitive function test by providing multiple means of filling in authentication information.

How to test

Tool: Visual inspection

Ensure that authentication form fields allow any of the following:

  • The fields allow autofill of information.
  • Information may be pasted into the form fields.
  • Biometrics can be used to sign into accounts.

Test outcomes

  • Pass: The authentication fields allow autofill of stored information OR information can be copied and pasted into the fields OR biometrics (fingerprints, facial-scan, etc.) can be used to log in.

  • Fail: The authentication fields do not allow autofill AND information cannot be copied and pasted into the fields AND biometrics cannot be used (for example: none of the pass criteria methods are used).

  • NA: The view does not require interaction to authenticate.

Related WCAG criteria

WCAG 2.2 AA - 3.3.8 Accessible Authentication

Diverse user needs (APP-3)

App language (APP-3-1)

The application language can be programmatically determined

How to test

Tool: VoiceOver (iOS) / Talkback (Android)

  1. Use the screen reader to interact with the application content.
  2. Ensure that the screen reader output matches the correct language for each language supported.

Test outcomes

  • Pass: The screen reader output matches the language of the application.

  • Fail: The screen reader output does not match the language of the application.

Related WCAG criteria

WCAG 2.2 A - 3.1.1 Language of Page

Warn about timeout (APP-3-2)

Users must be warned prior to when a session times out and expires.

How to test

Tool: Visual inspection

Confirm that users are warned prior to when a session times out and expires.

Test outcomes

  • Pass: Session timeout warning occurs prior to session time out and expiration.

  • Fail: Session timeout occurs without warning.

  • NA: No session timeout is present.

Related WCAG criteria

WCAG 2.2 A - 2.2.1 Timing Adjustable

Extend timeout (APP-3-3)

When a session timeout warning occurs, users MUST be given at least 30 seconds to take action in order to avoid a session timeout by extending the time limit via a simple user action.

How to test

Tool: Visual inspection

Confirm that users are given at least 30 seconds to take action in order to avoid a session time out by extending the time limit of a session.

Test outcomes

  • Pass: Users are given at least 30 seconds to extend the session.

  • Fail: Users are given less than 30 seconds to extend the session.

  • NA: No session timeout is present.

Related WCAG criteria

WCAG 2.2 A - 2.2.1 Timing Adjustable

Use an automated testing tool (APP-3-4)

For iOS devices, all Xcode - Accessibility Inspector Audit tests pass during development

For Android devices, all Accessibility Scanner tests pass during development

How to test

Tool: Xcode - Accessibility Audit (iOS)/Accessibility Scanner (Android

  1. Open your app in Xcode for iOS or Accessibility Scanner for Android.
  2. Start the accessibility tool used on your platform.
  3. Ensure that there are no automated errors present.

Test outcomes

  • Pass: Zero issues are found OR issues found are determined to be false positives by Visa Accessibility.

  • Fail: One or more issues are found.

Related WCAG criteria

WCAG 2.2 A & AA

These materials are intended for illustrative purposes only. They are provided AS-IS and should not be relied upon for marketing, legal, tax, financial, regulatory or other advice. Any links to third party sites are for your information only and do not constitute endorsement by or affiliation with Visa. Visa has no insight into and/or control over third party content and code and disclaims all liability for any such components.

Copyright © 2026 Visa. All rights reserved.