For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

Mobile App Accessibility Testing

Mobile app accessibility testing enables automated accessibility scanning for native mobile applications in KaneAI. This feature performs accessibility checks during test execution, helping identify accessibility issues and ensure compliance with accessibility standards.

Product boundary​

This page is for KaneAI-authored mobile flows. If you are triggering scans directly from Appium code, use Native App Automation Appium (Overview). If you want manual screen-by-screen validation on a real device, use Accessibility App Scanner (Overview).


Platform Support​

PlatformSupported VersionsNotes
iOS17.0 and aboveVersions below 17.0 will pass tests but won't generate accessibility reports
AndroidAll versionsFull support for accessibility scanning

How It Works​

Step 1: Add Accessibility Scan Instruction​

During test authoring, add the accessibility scan instruction:

  1. Navigate to the screen you want to scan
  2. Type "/" in the input box and click on Accessibility scan
  3. The instruction is recorded as part of the test flow
  4. The current screen is marked for accessibility scanning
add-accessibility-instruction

Step 2: Instruction Recording​

When the accessibility scan instruction is added:

  • The instruction is recorded in the test execution flow
  • The current screen is marked to be scanned using the app scanner hook for accessibility
  • The scan hook is triggered during test execution at the corresponding screen
accessibility-instruction-authored

Step 3: Test Case Creation​

Once the test is saved:

  • A test case is automatically created with the accessibility-scan tag
  • The accessibility scan instruction is visible in the test case summary
  • Use this tag to filter and identify tests that include accessibility scanning
test-case-summary

To view the screenshot of the screen where the accessibility scan was performed, click the (•••) icon.

accessibility-screenshot

Step 4: Execution and Reporting​

During automated test execution:

  • The accessibility scan is performed at the corresponding screen
  • Accessibility issues are detected and categorized
  • The accessibility report is available in the test execution results on Automation dashboard

Key Features​

FeatureDescription
Native App ScanningUses platform-native accessibility scan hooks
Automatic TaggingTests are automatically tagged with accessibility-scan for easy identification
Test Case IntegrationAccessibility instructions are visible in test case summaries
Automated ReportingAccessibility reports are generated during test execution
Cross-Platform SupportWorks on iOS 17+ and all Android versions

Troubleshooting​

No Accessibility Report Generated​

Possible Cause:

  • iOS version is below 17.0 (tests will execute but no report is generated)

Accessibility Scan Instruction Not Recorded​

Possible Causes:

  • Instruction not properly added during authoring
  • Test not saved after adding the instruction

Solutions:

  1. Verify the instruction was added correctly during authoring
  2. Ensure the test is saved after adding the accessibility instruction
  3. Check the test case summary for accessibility instruction visibility

Terminal First Testing With Kane CLI

Natural language browser & mobile app tests right from terminal.

×
Schedule Your Personal Demo
Kane CLI terminal

Help and Support

Related Articles