Scan content that opens outside your app on iOS devices

Scan content that Workflow Analyzer misses because the content opens outside your app on iOS devices.

Issue

When testing on iOS devices using Workflow Analyzer, certain screens, such as login pages, aren’t scanned for accessibility issues by App Accessibility testing. This issue occurs even when you deliberately navigate to the screens. The scan reports no issues for that screen and shows no error, so the screen looks like it passed. If your app has an Android version, the scan reports issues for the same screen when you scan the app on BrowserStack Android devices.

Cause

On iOS devices, screens that aren’t part of an app, such as login pages, are designed to open in the built-in Safari browser, through either SFSafariViewController or ASWebAuthenticationSession. Since iOS runs this browser as a separate process, the page isn’t included in your app’s view hierarchy. Because the App Accessibility rule engine reads only what your app renders, screens opened in the built-in browser aren’t scanned. This issue occurs whether or not Continuous Scanning is enabled because the App Accessibility rule engine uses the same view hierarchy for both.

On the other hand, Android renders web content inside the app process. As a result, the same screen is scanned when you use Android devices for testing.

Resolution

Scan the page in a desktop browser using Web Accessibility:

1. Note the URL of the page you want to check. Read the URL from the address bar in the built-in browser, or take the URL your app passes to SFSafariViewController or ASWebAuthenticationSession.
2. Scan that URL using Website Scanner.

Because the scan runs in a desktop browser, issues that appear only at mobile screen sizes, such as touch target size, might not be reported.

Related links

• Run Workflow Analyzer
• Configure settings
• Website Scanner overview