Deque • Enterprise software
axe DevTools Mobile tests native iOS and Android accessibility against the rendered accessibility tree.
Native mobile accessibility scanning for iOS, Android, React Native, Flutter, and .NET MAUI. Tests against the rendered accessibility tree (not HTML), so findings reflect what assistive technology actually interacts with. Available through Merito with per-platform SDK integration, CI gating, and audit-cycle wiring.
What it is
Mobile accessibility testing is fundamentally different from web. Web scanners read the HTML and CSSOM. Mobile assistive technology reads the rendered accessibility tree on each platform, which is constructed differently on iOS (UIKit, SwiftUI) and Android (XML views, Jetpack Compose). axe DevTools Mobile tests against that rendered accessibility tree directly, which means findings reflect what VoiceOver and TalkBack actually interact with.
Coverage spans native iOS (SwiftUI, UIKit), native Android (XML views, Jetpack Compose), and the cross-platform frameworks teams ship in production: React Native, Flutter, and .NET MAUI. Cross-platform code does not produce a single accessibility surface. Each platform build still requires separate test instrumentation because iOS and Android have different APIs, capabilities, and accessibility constraints. axe DevTools Mobile handles both platforms under one product.
The interactive testing model requires no source-code access. On Android, a floating action button overlays the running app and runs scans against whatever screen the developer is on. On iOS, the developer downloads the XCode project, plugs in a device, and clicks Play. No certificates, no device-management plumbing. For automated CI coverage, native SDKs integrate into XCUITest (iOS), Espresso and UI Automator (Android), and Appium (cross-platform).
Merito treats axe DevTools Mobile as the entry point to a mobile accessibility program rather than a drop-in scanner. Setup includes per-platform SDK integration, CI gating per platform build, React Native linting where the codebase warrants it, and audit-cycle integration with axe Auditor for the manual surface that automation cannot cover. Mobile accessibility programs are routinely under-staffed compared to web; this is the tooling that makes them feasible.
Ideal use cases
What it is best at
Mobile assistive technology reads what the OS exposes on the accessibility tree. axe DevTools Mobile tests against that surface directly, so findings match what VoiceOver and TalkBack actually announce. Web-style HTML-only mobile scanners miss the gap.
iOS and Android require separate test instrumentation even when the app is built with React Native or Flutter. Most accessibility scanners cover one platform; axe DevTools Mobile covers both with the same workflow.
Android's floating action button runs scans on any screen without rebuilding the app. iOS testing works from a downloaded XCode project with no certificates or device-management plumbing. Mobile accessibility champions can scan apps they did not build.
React Native, Flutter, and .NET MAUI codebases are explicitly supported, including React Native source linting for issues caught at the JSX layer before the app builds.
XCUITest on iOS, Espresso and UI Automator on Android, Appium for cross-platform. Pull-request blocking gates accessibility regressions per platform build inside the same CI configuration.
Core capabilities
Tests native iOS apps built with SwiftUI or UIKit against the iOS accessibility tree.
XCode project download workflow
Developer downloads the axe DevTools Mobile XCode project, plugs in a device, clicks Play. No certificates required. No device-management profile. The lowest-friction iOS accessibility scanner on the market.
Accessibility tree validation
Tests against the rendered iOS accessibility tree (the surface VoiceOver consumes), not the visual UI hierarchy. Findings match assistive-technology reality.
WCAG and iOS-platform rule mapping
Findings map to WCAG success criteria and iOS-specific accessibility requirements (Dynamic Type, VoiceOver labels, Switch Control compatibility).
XCUITest integration
Native SDK runs accessibility checks inside XCUITest specs as part of the standard iOS test suite.
Tests native Android apps built with XML views or Jetpack Compose against the Android accessibility tree.
Floating Action Button (FAB) interactive testing
Overlay FAB runs scans on whatever screen is currently active. No rebuild required. Useful for accessibility champions testing apps they did not author.
Accessibility tree validation
Tests against the rendered Android accessibility tree (the surface TalkBack consumes), with rules built specifically for Android-platform constraints.
WCAG and Android-platform rule mapping
Findings map to WCAG success criteria and Android-specific accessibility requirements (TalkBack labels, content descriptions, touch-target sizing).
Espresso and UI Automator integration
Native SDKs for both Android testing frameworks. Accessibility checks run as part of standard Android test suites.
First-class support for React Native, Flutter, and .NET MAUI with per-platform test execution.
React Native linting
Real-time accessibility linting at the JSX layer for React Native components. Catches issues during development before the app builds for either platform.
Flutter and .NET MAUI testing
Both frameworks tested via the per-platform SDK pattern. iOS builds tested with XCUITest; Android builds tested with Espresso or UI Automator.
Appium integration
Single Appium SDK handles cross-platform test runs for teams with existing Appium infrastructure.
Per-platform CI gating with pull-request blocking on accessibility regressions.
Platform-specific build gating
iOS and Android builds gated separately because the accessibility surface is different per platform. Findings forwarded to per-platform queues.
Pull request blocking
Configurable severity thresholds determine which findings block a PR merge. Mirrors the security-gate pattern engineering teams already accept.
AI-paired remediation
Pairs with the axe Assistant chatbot for in-context remediation guidance on mobile-specific accessibility findings.
Where it fits in the stack
First-party SDKs for the dominant mobile automation frameworks on both platforms.
Vendor-documented integration patterns for mobile CI hosts and build platforms.
Framework-specific integration paths for cross-platform mobile codebases.
Deployment and implementation
Licensing and packaging
axe DevTools Mobile Trial
Time-bound trial with the full feature set across iOS and Android.
Best for: Mobile teams evaluating before contract. Useful as a working preview rather than a feature-stripped demo.
axe DevTools Mobile
Full subscription tier with iOS, Android, and cross-platform framework coverage. CI integration plus Interactive testing plus React Native linting.
Best for: Mobile engineering organizations standing up an accessibility program with per-platform CI gating.
Merito services
Pick the engagement that matches where you are in the lifecycle.
WCAG and ADA program delivery built around mobile tooling. Audit playbook design for the mobile surface, governance, and ongoing run.
Explore service02Per-platform SDK integration, CI gating per platform build, React Native linting setup, interactive-testing rollout, and mobile-team handover.
Explore service03Per-platform mobile CI configuration with iOS and Android accessibility gates wired into the same pipeline graph.
Explore service04Mobile developer workshops on iOS and Android accessibility-tree concepts plus per-platform WCAG mapping.
Explore service05Named engineer, priority SLAs, and release-time coverage on the axe DevTools Mobile rollout across iOS and Android builds.
Explore service06Merito-placed mobile engineers experienced with axe DevTools Mobile, XCUITest, Espresso, and Appium accessibility test design.
Explore serviceaxe DevTools Mobile licensing
axe DevTools Mobile across iOS, Android, React Native, Flutter, and .NET MAUI, available through Merito with per-platform SDK integration, CI gating, and audit-cycle wiring.
Merito point of view
Merito's position. Most enterprises have a web accessibility program of some maturity and a mobile accessibility program that exists on paper. The tooling gap has been a real factor. Web has had axe-core for over a decade; mobile accessibility tooling has historically been weaker, fragmented across platforms, and dependent on test-framework expertise the mobile team usually does not have. axe DevTools Mobile closes that tooling gap.
Test the rendered accessibility tree, not the HTML or the visual UI. The accessibility tree is what assistive technology actually consumes on iOS and Android. Scanners that test against rendered HTML on a WebView miss most of the surface that matters. axe DevTools Mobile is one of the few mobile scanners architected against the accessibility tree directly.
iOS and Android are two separate accessibility surfaces. Cross-platform frameworks (React Native, Flutter, .NET MAUI) help share business logic, but each platform build produces its own accessibility tree with its own rules and conventions. Merito gates iOS and Android builds separately in CI, runs per-platform interactive testing, and pairs source-side React Native linting with build-side native scanning.
Mobile accessibility programs scale through tooling that mobile developers can actually run. The Android FAB pattern (no rebuild required) and the iOS XCode project download (no certificates) are deliberately low-friction. Merito frames axe DevTools Mobile rollouts around making accessibility scanning something the mobile team owns, not a quarterly audit somebody else does to them.
What buyers usually underestimate
Related from Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Consultation request
Share your mobile codebase shape (native iOS, native Android, React Native, Flutter, MAUI), your CI host, and your release cadence. A Merito mobile accessibility specialist follows up within one business day.
Two surfaces, one license
Most accessibility scanners cover one mobile platform. axe DevTools Mobile covers both with per-platform SDKs and a single license relationship.
Mobile-team-owned
The Android FAB pattern and the iOS XCode-project workflow are deliberately low-friction. Mobile accessibility programs scale when the mobile team owns the scanning.
Next step
A Merito axe DevTools Mobile conversation starts with the mobile codebase shape (native, React Native, Flutter, MAUI), the existing CI host, and the team that owns the mobile build pipeline. We scope per-platform.