Mobile
This section covers accessibility for native mobile apps on Android and iOS. It's for developers, QA engineers, and designers who want to understand an issue Evinced reported, or learn how to build accessible mobile apps. Choose an entry from the navigation, or use the search.
- Mobile Validations39 entriesOne entry per issue Evinced's mobile testing can report.
Mobile Validations
Each entry explains one issue that Evinced's mobile accessibility testing can report: what causes it, how it affects people, and how to fix it. Entries are named after the rule that reports the issue, such as label-in-name or tappable-area, so you can go straight from a test result to its explanation.
Every entry follows the same structure, described in How to read an entry. Mobile entries differ from web entries in a few ways.
Code examples by platform and framework
Pass and fail patterns are grouped in tabs by platform, with a tab for each framework:
| Platform | Frameworks |
|---|---|
| Android | XML Views, Jetpack Compose |
| iOS | UIKit, SwiftUI |
| Cross Platform | Flutter, React Native |
- Configuration files: when an issue is set in a configuration file rather than in code, the tab shows that file instead, such as the Android manifest or
Info.plist. - Design issues: issues that come from the design rather than the code, such as color contrast or text size, describe the values to use and have no code tabs.
- Missing frameworks: a framework appears only when there's an accurate example for it. If a framework you use isn't shown, the same approach usually applies with its own API.
- Single-platform issues: some issues exist on one platform only. Their description starts with "In Android apps" or "In iOS apps", and they show examples for that platform only.
Testing on a device
The Try It Yourself steps use the tools built into Android and iOS, such as a screen reader, voice input, an external keyboard, or developer tools. If you haven't used them before, start with these guides:
- Practical guides for using screen readers: TalkBack on Android and VoiceOver on iOS.
- Practical guides for using voice input: Voice Access on Android and Voice Control on iOS.
Standards for mobile apps
WCAG was written for the web, but most of its success criteria also apply to mobile apps. The standards table on each entry lists:
- WCAG 2.2, the success criterion the issue relates to.
- EN 301 549 clause 11, which applies WCAG to software, including mobile apps. A few web criteria, such as 2.4.1 Bypass Blocks, don't apply to software.
- Section 508, where it applies.
The Trusted Tester test process covers web content only, so it isn't listed on mobile entries.
Note: Some issues have both a web entry and a mobile entry with the same name, such as interactable-role or non-interactive-in-focus-sequence. Their content, and sometimes their severity, differ, because assistive technologies work differently on each platform. Make sure you're reading the entry for the platform you're testing.
Can't find what you're looking for? Write to us at knowledge@evinced.com.