Comprehensive test management solution for complex challenges.
Mobile App Accessibility Testing: 5 Key Areas and Common Issues
Discover five essential areas of mobile app accessibility testing, common barriers in checkout processes, and why manual testing matters.
An app can function flawlessly from a technical perspective and still be difficult or impossible for people with disabilities to use. Missing screen reader labels, truncated text, or inaccessible forms can prevent users from completing registration or placing an order.
Testing mobile apps for accessibility therefore involves more than checking technical requirements. It also means evaluating how accessible the app is in practice. What matters is whether people with different abilities can use the application's core features.
This article explains which requirements are relevant to mobile apps, which five testing areas deserve particular attention, and which accessibility barriers we encounter in our testing practice.
Why Mobile Apps Need Dedicated Accessibility Testing
Mobile apps differ from websites in how users interact with them. They rely on touch gestures, operating system-specific controls, and assistive technologies such as VoiceOver on iOS and TalkBack on Android.
Different screen sizes, individual font size settings, and alternative input methods add further complexity. An app must remain accessible under these conditions.
In our accessibility assessments, we regularly encounter barriers specific to mobile applications. An icon may be visually self-explanatory but announced by a screen reader simply as "Button". When users increase the font size, important controls may disappear, or forms may become impossible to use.
Testing a website for accessibility is therefore not enough to establish whether its corresponding app is accessible. Mobile applications require dedicated testing under realistic usage conditions.
What Legal Requirements Apply to Accessible Mobile Apps?
In Germany, several regulations provide the legal framework for digital accessibility. The applicable requirements depend primarily on the provider and the type of service offered.
The German Accessibility Strengthening Act (Barrierefreiheitsstärkungsgesetz, BFSG) has applied to certain products and services since June 28, 2025. This also includes mobile applications when they form part of a service covered by the Act, such as certain e-commerce services.
For federal public sector bodies, the relevant regulations include the German Disability Equality Act (Behindertengleichstellungsgesetz, BGG) and the Accessible Information Technology Ordinance (Barrierefreie-Informationstechnik-Verordnung, BITV 2.0). Public sector bodies at state level are subject to the applicable state regulations.
EN 301 549, WCAG, and WCAG2ICT as Testing Foundations
Three key references are particularly relevant when evaluating technical accessibility:
- EN 301 549: This European standard defines accessibility requirements for information and communication technology, including software and mobile applications.
- WCAG (Web Content Accessibility Guidelines): These guidelines define testable accessibility requirements, including color contrast, labeling, and operability.
- WCAG2ICT: This W3C publication provides guidance on applying relevant WCAG requirements to non-web information and communication technologies, including software. It is a supporting technical guidance document, not a standalone law.
Meeting technical accessibility criteria is important. However, whether an app is genuinely accessible becomes clear through practical testing.
Mobile App Accessibility Testing: The 5 Key Areas
When testing mobile applications for accessibility, we focus on five particularly important areas. These help determine whether information is perceivable, controls can be accessed, and essential processes work with assistive technologies.

1. Screen Reader Support with VoiceOver and TalkBack
Screen readers enable blind and visually impaired users to navigate apps through speech output and specific navigation gestures. VoiceOver is used on iOS, while TalkBack is available on Android.
During testing, we navigate through the app's core functions with the screen reader enabled. We check whether controls have meaningful labels, content follows a logical reading order, and status changes are announced correctly.
A typical issue involves buttons without descriptive labels. Instead of announcing "Add to cart," for example, the screen reader may simply say "Button." Users then have no way of knowing what action the control performs.
We have encountered similar situations in practice. Error messages can also cause problems. If they are displayed only visually, users may not understand why a form could not be submitted.
The key question is whether users can understand and complete an entire process with a screen reader enabled.
2. Font Sizes and Display Adjustments
Many people increase the font size on their smartphones to make content easier to read. Mobile apps must respond to these settings without making important information or functionality inaccessible.
During testing, we increase the font size through the operating system settings and then review the relevant screens again.
Common issues include truncated text, overlapping input fields, and buttons that can no longer be reached.
These problems are particularly critical in registration and checkout forms. If instructions disappear or the button needed to continue becomes hidden, users may be unable to complete the process.
Increasing text size must not compromise usability or accessibility.
3. Portrait and Landscape Orientation
Changing a device's orientation can significantly affect how an app is displayed. We therefore check whether content and functionality remain accessible in both portrait and landscape orientations.
Forms, dialog boxes, and navigation elements require particular attention. A typical problem occurs when buttons move outside the visible screen area after switching to landscape orientation and can no longer be accessed.
Dialog boxes may also obscure important information when the layout changes.
There are limited exceptions when a particular orientation is essential to the content or functionality. Examples include the presentation of a bank cheque or a piano keyboard. Outside such cases, an app should not unnecessarily restrict users to a single orientation.
4. Keyboard Accessibility and Focus Management
Not everyone interacts with mobile applications exclusively through a touchscreen. External keyboards and other assistive input devices can provide important alternatives.
During accessibility testing, we check whether relevant controls can be reached using alternative input methods and whether the focus order is logical and predictable.
Common problems occur when focus moves unexpectedly, individual elements are skipped, or users cannot exit an open dialog box.
Such issues make navigation difficult and can completely block access to essential functionality.
Consistent focus management is particularly important in multi-step processes, where users must be able to reach the next step reliably.
5. Color Contrast and Visual Indicators
An accessible app must present information in a way that remains understandable for people with visual impairments or color vision deficiencies.
This includes sufficient color contrast and indicators that do not rely on color alone.
A common example is an incorrectly completed input field that is marked only with a red border. Without an additional error message, some users may not understand what needs to be corrected.
We therefore check whether text and controls are clearly visible and whether errors, required fields, and status changes are communicated unambiguously.
Beyond these five areas, a comprehensive accessibility assessment must consider all other applicable requirements. These include, for example, touch targets that are sufficiently large and easy to reach.
Common Accessibility Barriers in Checkout Processes: When Individual Issues Block Completion
Accessibility problems become particularly apparent in multi-step processes such as registration, login, or checkout.
In our accessibility assessments, we observe recurring issues: buttons without labels, illogical focus order, truncated content, and error messages that are not announced by screen readers.
One example: A person fills out an order form while using a screen reader. After submitting the form, an error message appears because a required field is missing. However, the message is not read aloud. It remains unclear to the person why the ordering process cannot continue.
Another example from our testing practice involved a form for entering bank details, including an IBAN and account holder information. When an entry was invalid, the application displayed a message instructing users to correct the "fields marked in red."
This caused two accessibility problems. First, the message relied on color alone to identify the affected fields. Second, the error was not automatically announced by the screen reader. Users relying on speech output therefore received insufficient information to identify and correct the problem.
Small or closely spaced touch targets can also cause difficulties. People with motor impairments may unintentionally select the wrong option.
These examples show why testing individual controls is not enough. What matters is whether users with different abilities can successfully complete their tasks.

How Does Mobile App Accessibility Testing Work?
A structured mobile app accessibility test begins by identifying relevant user journeys. Functions that are essential to the app's purpose deserve particular attention, such as registration, login, product search, and checkout.
For testing, we use Android and iOS devices running the latest operating system versions. On these same devices, we enable assistive technologies such as TalkBack and VoiceOver and adjust settings such as text size or alternative input methods.
During testing, accessibility barriers are reproduced and documented. A useful defect report includes the test environment, reproduction steps, expected and actual behavior, and the impact on accessibility and usability.
The findings provide a basis for prioritizing and fixing issues. Once a problem has been corrected, the affected functionality should be tested again.

Automated or Manual Accessibility Testing: Which Is Necessary?
Automated accessibility testing tools can identify certain technical issues, such as missing accessibility labels or specific color contrast problems. The issues they can detect depend on the tool and the app's technical implementation.
Automated checks can support repeatable testing, but they cannot replace manual assessments.
Whether a focus order makes sense, a screen reader communicates the correct information, or a checkout process can be completed must be evaluated in the actual usage context.
In our accessibility projects, we therefore combine automated analysis with manual expert testing on real devices.

Automation helps identify certain issues efficiently. Manual testing reveals how accessibility barriers affect real-world use. Both approaches complement each other.
Learn more about integrating accessibility into quality assurance in our article Accessibility as a Service.
Conclusion: Accessible Mobile Apps Require Practical Testing
The accessibility of mobile applications cannot be evaluated through technical test results alone. Practical testing with screen readers, larger font sizes, and alternative input methods reveals where users encounter barriers.
The five testing areas described in this article help identify common accessibility issues early. Testing complete user journeys is particularly important because even a single issue can prevent users from completing registration or placing an order.
Organizations that systematically integrate accessibility into software development and quality assurance can address these problems more effectively and improve the usability of their apps.
Would You Like to Assess Your App's Accessibility?
andagon provides accessibility testing and assessment services for mobile applications as well as websites.
Find out more about andagon's accessibility services and how we support organizations in evaluating the accessibility of their digital applications.