How do I test iOS app accessibility?

For iOS (Swift/SwiftUI/UIKit): enable VoiceOver and navigate the app by swiping. Set accessibilityLabel on all interactive elements. Use Dynamic Type via scaledFont(for:) with adjustsFontForContentSizeCategory = true. Test in Xcode Accessibility Inspector. Upload screenshots to AccessiSight mobile scanner for automated WCAG 2.2 checks.

How do I test Android app accessibility?

For Android: enable TalkBack and navigate the app. Set android:contentDescription on all ImageView and ImageButton elements. Use android:labelFor to link labels to inputs. Enable Display Size and Font Size scaling to test reflow. Use Android Accessibility Scanner app for automated checks. Upload screenshots to AccessiSight for WCAG 2.2 analysis.

What React Native props are needed for accessibility?

Key React Native accessibility props: accessibilityRole (button, link, header, checkbox, etc.), accessibilityLabel (announces element name), accessibilityHint (describes what happens on activation), accessibilityState ({ checked, selected, disabled, expanded }), accessibilityValue for sliders/progress bars, accessible={true} to group children as a single element. All map to WCAG 4.1.2 (Name, Role, Value).

What is the minimum touch target size for accessibility?

WCAG 2.5.8 (AA) requires a minimum 24×24 CSS pixels for touch targets. Apple HIG recommends 44×44 points. Material Design recommends 48×48 dp. Always add padding to small icons rather than making the visual element larger, to achieve the minimum touch area without changing the design.

Can I integrate mobile accessibility scanning into CI/CD?

Yes, two ways. POST /api/scan/mobile accepts multipart screenshot uploads for an advisory visual review when the server has a vision model: send screenshots from Detox, Appium, XCUITest, or Espresso. Or POST /api/mobile-scan accepts a structured native accessibility tree (captured via XCUITest's XCUIElementSnapshot, UIAutomator's AccessibilityNodeInfo dump, or your React Native/Flutter test harness) for deterministic checks like missing labels and touch-target size, with no screenshot required. Both responses include a severity field you can use to fail your CI build on critical or serious issues.

Native Mobile App Accessibility Scanner

Scan Mobile Apps for Accessibility

Scan your mobile web app's URL for an automated accessibility audit under real mobile device emulation, and get a platform-specific WCAG 2.2 checklist for iOS, Android, React Native or Flutter that you can track and export. Screenshot review of native app screens is optional and needs a configured vision model.

WCAG 2.2 AAVoiceOver / TalkBackTouch TargetsContrastReflowEN 301 549

An AccessiSight report open on a phone: the Accessible University demo page scores 73 out of 100, with 48 issues found.

1Select Platform

2Scan a live URL (recommended: runs a real automated scan)

Enter the URL of your mobile web app (or your site's mobile view). We run our full accessibility engine against it under a mobile device emulation profile (mobile viewport, user agent, and touch input), so touch-target sizing, reflow, and other findings reflect a phone-sized layout, not a desktop layout relabeled as mobile.

Website or app URL

Runs under Chromium's mobile device emulation (mobile viewport, user agent, and touch input), not a real iOS Safari or Android Chrome render. For a native iOS, Android, React Native or Flutter app that already captures its own accessibility tree, see the native-tree endpoint below.

Already have a native accessibility tree?

If your app is instrumented with XCUITest, UIAutomator, or a React Native/Flutter test harness, POST your captured native accessibility tree directly to /api/mobile-scan for deterministic touch-target and missing-label checks. No URL or screenshot needed. See the SDK tab below for details.

3Upload Screenshot (optional: a visual review by a vision model, when the server has one)

Without a screenshot, you get the full platform checklist. A screenshot adds an optional visual review where a vision model is configured.

Drag & drop or click to upload

PNG, JPEG or WEBP, max 10MB

What We Check

Automated mobile scan

Enter a URL and we run this app's full WCAG detection engine (the same one behind the desktop scanner) against it under mobile device emulation, catching touch-target, reflow, and mobile-specific issues, not a static checklist.

AI Visual Analysis

Upload a screenshot for an advisory visual review (contrast, unclear icons, crowded layouts) by a vision model, when the server has one. Without one, you get the platform checklist and no credit is used.

WCAG 2.2 Checklist

16 platform-specific checks covering touch targets, reflow, text resize, screen reader compatibility, gesture alternatives, motion, and authentication.

React Native Specific

accessibilityRole, accessibilityState, accessibilityHint, accessibilityActions: the exact props your developers need to set, mapped to WCAG criteria.

CI/CD Integration

REST API accepts screenshots from Detox, Appium, XCUITest, Espresso. Fail your builds automatically when critical accessibility regressions are detected.

Android (TalkBack) Rules

contentDescription, importantForAccessibility, labelFor: the Android attributes TalkBack needs, checked against WCAG 4.1.2.

iOS (VoiceOver) Rules

accessibilityLabel, accessibilityTraits, Dynamic Type support (scaledFont), accessibilityContainer: rules for full VoiceOver compatibility.

Frequently Asked Questions

Web Scanner WCAG 2.2 Guide ADA Compliance EAA 2025 Accessibility Glossary Academy