- Runs on your build
- Point the CLI at a connected device or emulator plus a short guided-flow file, and it walks the app screen by screen — exactly what a real user, and their screen reader, would touch. Hosted, zero-touch mobile scanning is on the roadmap.
- One pipeline, web + mobile
- Mobile findings flow through the same review queue, the same VPAT 2.5 INT / ACR, the same client status portal and regression alerts as the web scanner — one conformance story across every surface.
- Source-native remediation
- Findings arrive with developer-ready fixes in the app’s own idiom — an accessible name, a 48dp target, a contrast-safe textColor — never a client-side overlay.
- Media without the manual upload
- Bundled media is extracted from the APK and streamed HLS/DASH manifests are discovered automatically; the owner supplies only what a scan genuinely can’t reach (DRM). Captions and audio description are then judged, not guessed.
- Cross-screen consistency
- Navigation order, control identification, help placement, and redundant re-entry are evaluated across the whole flow — not one screen in isolation.
- Batch app audits
- Scan a list of apps into one comparative report — built for portfolios and agency reviews.
- Honest by construction
- Every verdict states how it was reached. A criterion a scan can’t measure is marked Not Applicable with a reason, or confidence-scored and routed to a one-click reviewer step — the same standard the VPAT reports, never a silent guess.
- No third-party engine
- The whole thing is our own evaluators over the platform accessibility APIs — the same in-house philosophy as the web scanner, so there’s no black-box rules engine to reconcile with your findings.