Mobile Accessibility Testing: iOS 18 and Android 15 New Features
The way people interact with the digital world is increasingly happening on mobile devices. This shift makes mobile app accessibility more important than ever. For developers and testers, staying current with the latest changes in mobile operating systems isn’t just about new features, it’s about ensuring everyone can use your app. With iOS 18 and Android 15 introducing fresh updates to their screen readers, the methods for testing mobile accessibility are also changing.
This article gives you a practical look at what’s new and how to adjust your testing. We’ll cover the specific updates to VoiceOver and TalkBack, review mobile-specific testing requirements for 2025, and compare the best tools for the job. You’ll get actionable advice to help you build and maintain apps that are usable by people with a wide range of disabilities.
Mobile Accessibility Testing Urgency in 2025
Making mobile apps accessible is no longer a niche concern; it’s a business necessity. In 2025, the reasons to prioritize mobile accessibility are stronger than ever, driven by both legal requirements and the simple reality of how many people depend on their phones. Ignoring accessibility means shutting out a large portion of potential users and exposing your organization to legal risks.
The conversation has moved beyond “why” and is now firmly focused on “how.” Teams that integrate accessibility testing into their workflow from the beginning are not just complying with laws; they’re building better, more user-friendly products for everyone.
Legal Requirements for Mobile Apps
Legal pressure for digital accessibility is growing worldwide. In the United States, lawsuits related to the Americans with Disabilities Act (ADA) have been increasing, with thousands of cases filed annually. While the ADA doesn’t explicitly mention websites or mobile apps, courts have repeatedly ruled that they are considered “places of public accommodation.” This means your mobile app must be accessible to people with disabilities.
In Europe, the European Accessibility Act (EAA) set a deadline of June 2025 for many products and services to be accessible. This includes mobile apps, which must work with assistive technologies and follow established standards. For businesses operating globally, adhering to these rules is not optional. Failing to meet these requirements can lead to fines and legal action, making accessibility a matter of risk management.
User Statistics Driving Mobile Accessibility
The number of people who rely on mobile accessibility features is substantial. While exact figures vary, they represent a significant user base that can’t be ignored. These users depend on features like screen readers, voice commands, and text resizing to navigate apps and access information.
When an app doesn’t work with VoiceOver or TalkBack, it’s not a minor inconvenience, it’s a complete barrier. A button without a label is unusable for a screen reader user. Text that doesn’t resize can be impossible to read for someone with low vision. By making your app accessible, you are expanding your audience to include millions of people who would otherwise be unable to use your product. Thinking about these users from the start is the key to creating an app that truly serves everyone.
iOS 18 VoiceOver Testing: New Features and Methods
Apple’s VoiceOver screen reader has long been a central part of the iOS experience, and the updates in iOS 18 continue to refine how users interact with their devices. For testers, these changes mean adapting testing procedures to account for new capabilities and user expectations. The latest version introduces more customization and smarter recognition features that can change how a person with a visual disability navigates an app.
Testing on iOS is not just about checking for compliance; it’s about understanding the user experience. Does your app work smoothly with the new VoiceOver features? Is the navigation logical and intuitive? These are the questions testers need to ask.
Enhanced Voice and Audio Control
iOS 18 brings more detailed control over the VoiceOver experience, which testers need to be aware of. One of the main updates is the new “Voices” rotor item, which allows users to add and switch between multiple voices, including their own personal voice. This means a user could have different voices for reading text versus navigating menus. When testing, you should check if your app’s content is read clearly and correctly regardless of the selected voice.
Another change is to Audio Ducking, which lowers the volume of other audio while VoiceOver is speaking. Users now have three options: “Off,” “When Speaking,” and “Always”. Testers should verify that audio in their app (like background music or video playback) responds correctly to these settings. For example, if a user has it set to “When Speaking,” does your app’s audio volume lower as expected and return to normal afterward? A new startup haptic also gives users vibration feedback when VoiceOver turns on, a small but useful confirmation.
Improved Image and Scene Recognition
A significant change in iOS 18 is the consolidation of recognition features into a single rotor item called “Live Recognition”. This feature can now detect text, people, doors, and furniture simultaneously and starts speaking immediately when activated.
For testers, this has a few implications. First, you need to check how Live Recognition interacts with your app. Does it correctly identify text within images or custom UI elements? The feature is designed to fill in gaps where developers haven’t provided information, but it’s not a replacement for good accessibility practices. Always provide alternative text for important images. An automatically generated description might be helpful, but a well-written alt text from the developer will almost always be more accurate and contextually appropriate. Testing with Live Recognition can show you where your app has gaps in its accessibility information.
Updated Testing Procedures for iOS 18
With the new features in iOS 18, your testing checklist should be updated. Here are a few things to focus on:
Check the Delay Before Selection: A new setting allows users to add a delay before an item is selected, which helps prevent accidental taps. Test your app’s interface to make sure it remains responsive and that this delay doesn’t cause unexpected behavior with custom gestures or controls.
Test with the Voices Rotor: Switch between different voices to ensure your app’s content is pronounced correctly. Check for any issues with custom fonts or unusual text.
Verify Audio Ducking: Play audio or video in your app and activate VoiceOver. Confirm that the audio level adjusts according to the user’s Audio Ducking setting.
Use Live Recognition: Activate Live Recognition within your app to see what it detects. Use this as a tool to find images that are missing alt text or controls that aren’t properly labeled. It can help you find areas where the user experience relies too heavily on vision.
Android 15 TalkBack and Accessibility Services
On the Android side, Google is also pushing forward with updates to its accessibility tools. TalkBack, the native Android screen reader, gets some important improvements in version 15, and other services like Switch Access continue to evolve. Android’s open ecosystem means that accessibility can sometimes feel less consistent than on iOS, but the latest updates show a clear direction toward more intelligent and helpful features.
For testers, staying on top of Android’s changes is just as important. The diversity of devices and manufacturer skins (like Samsung’s One UI) means you often have to test on more than one device to get a full picture.
TalkBack Improvements and Testing Changes
The headline feature for TalkBack 15.0 is the introduction of more detailed image descriptions powered by Gemini, Google’s AI. When a user comes across an image without alt text, they can now ask for a detailed description generated by AI. This is a big step up from the older, less reliable on-device descriptions.
As a tester, you should see this feature as a safety net, not a solution. Your primary goal is still to ensure that all meaningful images in your app have developer-provided alt text. Here’s how to adjust your testing:
- Identify Images Without Alt Text: Use TalkBack to navigate your app and find any images that are announced as “unlabeled.”
- Test the “Describe Image” Feature: For those unlabeled images, use the “Describe image” option in the TalkBack menu to see what Gemini generates. Is the description accurate? Does it make sense in the context of your app?
- Prioritize Manual Fixes: Even if the AI description is good, the best practice is to add your own alt text. An AI can’t understand the specific purpose of an image in your app’s unique user flow.
TalkBack 15 also refines continuous reading, which now starts from the currently focused item instead of the next one. This is a more intuitive behavior that testers should verify works as expected in long-form content within their apps.
Switch Access and Voice Access Updates
Beyond TalkBack, Android offers a suite of accessibility services for users with motor impairments. Switch Access allows users to control their device using switches instead of the touchscreen, while Voice Access provides hands-free control through voice commands.
Testing for these services is often overlooked but is a part of a thorough mobile testing plan.
- Switch Access Testing: Can a user navigate your entire app using only one or two switches? Check if all interactive elements are focusable and can be activated. Pay special attention to custom controls or complex gestures that might not be compatible with switch-based navigation.
- Voice Access Testing: Review your app to see if buttons and controls have clear, spoken labels. Voice Access relies on these labels. For instance, if a button has a visible label that says “Submit,” a user should be able to activate it by saying “Tap Submit.” If the accessible name is different or missing, voice commands may fail.
Android Accessibility Scanner Evolution
Google’s Accessibility Scanner is a tool that automates some parts of accessibility testing. It scans your app and provides suggestions for improvements, such as increasing touch target sizes, adding labels, and improving color contrast. While it’s not a substitute for manual testing with TalkBack, it’s an excellent first step for any development team.
The scanner helps you catch common problems quickly. For 2025, tools like this are becoming smarter and more integrated into the development process. Testers should run the scanner early and often to catch low-hanging fruit, which frees up manual testing time to focus on more complex issues like user flows and logical navigation order. Think of it as a spell checker for accessibility, it won’t write the book for you, but it will catch a lot of common mistakes.
Mobile-Specific Testing Requirements in 2025
Testing for mobile accessibility involves more than just screen readers. The nature of touchscreen devices creates unique challenges and requirements that don’t exist on the desktop. In 2025, as mobile devices become even more central to daily life, getting these mobile-specific details right is more important than ever.
From the size of a button to how an app responds when you turn your phone sideways, these factors can make the difference between a usable app and a frustrating one for people with disabilities. A good mobile testing plan must account for these elements.
Touch Target Size and Spacing Standards
Have you ever tried to tap a small button or link on a mobile website and accidentally hit the one next to it? This is a common frustration, and for users with motor impairments, it can make an app unusable. WCAG (Web Content Accessibility Guidelines) has rules for touch target size for this very reason.
A sufficiently large touch target makes it easier for everyone to interact with your app, but it’s especially helpful for users who may have difficulty with fine motor control. When testing, you need to verify that all interactive elements, buttons, links, form fields, are large enough to be easily tapped. Don’t just rely on visual inspection. Use a tool that can measure the actual size of the targets on the screen. Also, check the spacing between targets. If they are too close together, accidental taps are more likely.
Gesture Alternatives Implementation
Many mobile apps rely on complex gestures, like swiping to delete an item or pinching to zoom. While these can be efficient for some users, they can be impossible for others, such as someone using a screen reader or a switch device.
For every action that requires a complex gesture, there must be a simpler alternative. For example, if swiping a list item reveals a “delete” button, there should also be a way to access that button without swiping, perhaps through a long press or an “edit” mode. During testing, your job is to identify every gesture-based action in the app and confirm that a simple, accessible alternative exists. This ensures that all users can access the same functionality, regardless of their ability to perform specific gestures.
Screen Orientation and Zoom Testing
People use their phones in both portrait and landscape mode. Your app should be fully functional in both orientations. When you rotate the device, the layout should adapt without cutting off content or hiding important controls. For a user who has their device mounted in a fixed position (for example, on a wheelchair), an app that only works in one orientation can be a complete barrier.
Similarly, users with low vision often rely on their device’s zoom or magnification features to read text. Your app must support this. When a user zooms in, the text should reflow to fit the screen so they don’t have to pan back and forth to read each line. Test your app by enabling the system’s magnification feature and increasing the font size. Does the layout adjust gracefully, or does it become a jumbled mess? All content should remain visible and usable, no matter the text size or orientation.
Automated Mobile Testing Solutions
Automated tools can scan your app and flag common accessibility issues in minutes. They are perfect for integrating into your development pipeline to catch problems early.
- Google’s Accessibility Scanner: This free Android app scans your screen and provides suggestions to improve accessibility, like increasing touch target sizes or adding content labels. It’s a great starting point for any team.
- Deque axe-core: Deque’s automated testing engine, axe-core, is a leader in the field and can detect a significant percentage of accessibility violations with no false positives. Deque offers tools for mobile that can identify platform-specific issues on both Android and iOS, helping you find problems with touch target sizes or voice control support.
- Pa11y: While primarily focused on web content, Pa11y’s command-line interface can be used to test web-based views within mobile apps. It’s highly configurable and excellent for running large-scale tests as part of a continuous integration process.
Here is a quick comparison of these popular automated tools:
Manual Device Testing Services and Tools
Automation can only get you so far. To truly understand the accessibility of your mobile app, you have to test it manually with the same tools that people with disabilities use every day.
- VoiceOver (iOS): This is the screen reader built into every iPhone and iPad. Learning to use VoiceOver is non-negotiable for anyone testing on iOS. You need to be able to navigate your app, activate controls, and access all functionality using VoiceOver gestures. Pay close attention to the focus order, control labels, and the rotor for navigation.
- TalkBack (Android): TalkBack is the Android equivalent of VoiceOver. It provides spoken feedback and has its own set of gestures for navigation. Because of the variety of Android devices, it’s a good idea to test on a few different models, such as a Google Pixel and a Samsung Galaxy, as the experience can differ.
- User Testing: The most valuable form of manual testing involves getting feedback from users with disabilities. These users bring their lived experience and can uncover issues that automated tools and non-disabled testers would never find. Engaging with the disability community for feedback is one of the most effective ways to discover and fix real-world barriers.
Creating Mobile Testing Plans
A structured testing plan is what separates haphazard checking from a professional quality assurance process. Without a plan, it’s easy to miss critical user flows or forget to test important features. A good plan ensures your testing is consistent, repeatable, and covers all the key aspects of your app.
Your plan should be a living document that outlines what you’re testing, how you’re testing it, and what devices you’re using. It brings order to your efforts and creates a record of your findings, which helps your team track progress and avoid repeating the same mistakes.
For a mobile app, your test plan should focus on the core user journeys. In an e-commerce app, for example, that means testing everything from searching for a product to adding it to the cart and completing the checkout process. Each of these flows should be tested using different accessibility tools, including screen readers and magnification. Document which OS versions and devices you are testing on, as an issue on one version of Android might not appear on another.
Common Mobile Barriers and Quick Fix Solutions
Many mobile apps stumble on the same basic accessibility issues. By being aware of these common pitfalls, you can spot them quickly during your testing and work with your developers to fix them.
- The Problem: Icons and buttons have no text labels. A screen reader user just hears “button, unlabeled”.
- The Problem: The focus order is illogical. When a screen reader user swipes through the screen, the focus jumps around randomly instead of following the visual layout.
- The Fix: Developers need to check the native view hierarchy to ensure the order of elements makes sense. The focus should typically move from top to bottom and left to right.
- The Problem: Images that convey information are missing alt text.
- The Problem: Touch targets are too small or too close together.
- The Fix: Use a design tool or accessibility scanner to measure the touch targets. Ensure they meet the minimum size recommendations from WCAG and have adequate spacing between them.
- The Problem: Text doesn’t get bigger when the user increases the system font size.
- The Fix: Developers should use scalable text units (like SP on Android) instead of fixed pixel sizes. This allows text to resize based on the user’s system preferences.
Best Mobile Accessibility Testing Tools Comparison
Choosing the right tools is a big part of creating an effective mobile accessibility testing process. There’s no single tool that does it all; instead, the best approach is to combine automated scanning with manual testing on real devices. This hybrid method allows you to catch a wide range of issues, from simple mistakes to complex user experience problems.
Automated tools are great for speed and efficiency, quickly finding common violations across your app. Manual tools, including the native screen readers on iOS and Android, are essential for understanding how your app actually feels to a person using assistive technology.
Using Automated Tools for Quick Insights (Accessibility-Test.org Scanner)
Automated testing tools provide a fast way to identify many common accessibility issues. They can quickly scan your website and point out problems that might be difficult for people with disabilities to overcome.
Visit Our Tools Comparison Page!
Run a FREE scan to check compliance and get recommendations to reduce risks of lawsuits
Final Thoughts
Are you ready to find and fix the accessibility issues in your mobile app? Start by running a free scan with the Accessibility-Test.org website scanner to get instant feedback on your site’s accessibility.
Start your compliance journey, update your accessibility statement, and keep EAA top of mind in every project going forward.
Run a Free Scan to Find E-commerce Accessibility Barriers
Want More Help?
Try our free website accessibility scanner to identify heading structure issues and other accessibility problems on your site. Our tool provides clear recommendations for fixes that can be implemented quickly.
Join our community of developers committed to accessibility. Share your experiences, ask questions, and learn from others who are working to make the web more accessible.