Appium WebdriverIO

Use this guide when WebdriverIO orchestrates Appium tests for Android or iOS. Accessibility is enabled on the remote options object, and you call lambda-accessibility-scan from async tests or hooks.

Prerequisites

WebdriverIO + @wdio/appium-service (or your chosen runner) configured for TestMu AI
App artifact available to the grid
Accessibility entitlement

Onboarding path

1. Set capabilities in `wdio.conf.ts` (or `.js`)

export const config = {
  capabilities: [{
    platformName: 'Android',
    'appium:deviceName': 'Pixel.*',
    'appium:app': 'lt://APP_ID',
    'accessibility': true,
    // 'accessibility.autoscan': true,
  }],
  // host/user/key per your standard WDIO LambdaTest preset
};

Match keys to your Appium server version (appium: prefix for W3C caps).

note

To scan every screen your test reaches without a hook call at each one, set accessibility.autoScan to true on the session. See AutoScan for Mobile App Accessibility. Keep the hook where you need a scan at an exact moment.

2. Call the hook after screens load

await browser.execute('lambda-accessibility-scan');

Use WDIO’s waitUntil patterns before executing the hook so dynamic content is present.

3. Run the suite

npx wdio run wdio.conf.ts

4. Review Accessibility results

Same dashboard path as other mobile automation (overview).

Troubleshooting

Symptom	What to check
`execute` undefined	Ensure the session is still active and you are not using a mocked driver in unit tests.
No report	Missing `accessibility: true` or hook never awaited.

Prerequisites​

Onboarding path​

1. Set capabilities in wdio.conf.ts (or .js)​

2. Call the hook after screens load​

3. Run the suite​

4. Review Accessibility results​

Troubleshooting​

Related docs​

Terminal First Testing With Kane CLI