Accessibility testing and execution evidence
Configure accessibility testing
Enable Send BrowserStack accessibility testing with each session in AIQ, choose the standard and issue categories, and set a stable project name. BrowserStack’s automated accessibility overview describes its SDK/reporting model; the Appvance controls below govern the integrated implementation.
Accessibility enabled
On
Runs registration/scans only when the DS target gate permits them and BrowserStack accepts registration. Off means no accessibility registration, scan or report.
Accessibility standard
WCAG 2.1 AA
WCAG 2.0 / 2.1 / 2.2 at A, AA or AAA; or RGAA. Choose the standard required by the project.
Issues needing review / experimental / advanced
On / on / on
Select which additional issue categories to include.
Best-practice recommendations
Off
Optional advisory category.
Scan automatically after page changes
On
Despite this UI label, DS currently scans
before
relevant page-changing playback actions and once at stop. With automatic scanning off, only the final scan runs.
Project name
Blank
Keep a stable nonblank name to group reports and enable direct report links. Blank can lead to a dashboard-only link.
Target eligibility versus verified scans
Chrome 100+ on Windows/macOS
Eligible.
Windows 11 Chrome verified; other combinations still need acceptance.
Safari on macOS Sequoia, Tahoe or Golden Gate
Eligible. Scanned with BrowserStack's in-page scanner; no accessibility capability is sent (since 17 Nov 2026).
Golden Gate verified live through DSServer on 17 Nov 2026: 2 scans, results saved, processed report (94 issues, score 49). Tahoe and Sequoia not yet run with the current build.
Chrome on Android 15+
Eligible in code.
DS live accessibility acceptance pending, including Android 17 starter.
Safari on iOS 18+
Eligible in code.
DS live accessibility acceptance pending.
Edge / Firefox / older targets
Skipped by DS.
A functional cloud run can still proceed without scans.
Provider support varies by framework. BrowserStack now documents Edge for selected SDK frameworks. Its TestNG guide and Playwright guide also differ on iOS and Android details. The table above describes DSServer’s current gate, not universal BrowserStack certification. A catalog entry or accepted capability does not prove scans ran.
Compare the current TestNG support matrix, Playwright support matrix and provider troubleshooting guide when investigating a target or entitlement issue.
What happens during a run
DSServer registers the build, obtains provider scanner data, attaches the required token to the cloud session, reports a test run, scans during playback, and saves/finalizes at stop. Merely sending accessibility=true produced no scans in earlier checks; the current implementation performs the additional SDK lifecycle steps.
These steps use BrowserStack’s internal SDK protocol and can change on the provider side. Failures are best effort and logged; they do not automatically fail the DesignerScript. Scanning adds latency to affected actions, so measure representative workflows before increasing concurrency.
Desktop Safari (since 17 Nov 2026**).** BrowserStack's scan script normally waits for BrowserStack's browser extension to appear in the page. For Safari, the accessibility capability made BrowserStack set up its "Accessibility Toolkit Headless" Safari extension. Its setup window could stop Safari from starting ("timed out while connecting to a Safari instance"), and the extension never reached the page, so every earlier Safari scan answered "Scanner is not ready on the page after multiple retries." DSServer now sends no accessibility capability for desktop Safari and runs the script's in-page mode, which phones also use: it loads BrowserStack's scan engine into the page itself. That mode runs no advanced rules and depends on the account's mobile-scanning switch. A scan reply that says it did not scan now counts as a failed scan, and its message is logged.
Final playback step. The collectBrowserStackData step, which logged the run's BrowserStack data at the end of a playback, was added on 16 Nov 2026 and turned off on 17 Nov 2026, because it did not work in scenario runs. Results are still saved when the session stops, and the final report is still logged by DSServer.
Open the final report
Stop the test so results are saved and the build can finish processing.
Follow the report=… link in the DS operational log, or open Accessibility → Automated Tests.
Choose the configured project and the exact AIQ-… build. Review severity counts, score, pages, components and needs-review items.
Use the BrowserStack accessibility final report log line for processed counts. The preliminary summary is not the final result.
If the final report is delayed, allow processing time. DS starts checking after 30 seconds, repeats every 30 seconds and gives up after 10 minutes without keeping the browser session open.
Two dashboard pitfalls: the Automate build’s own Accessibility tab still showed “not enabled” in the recorded integrated runs; the actual report was in the separate Accessibility product. Test health can appear red because DS currently reports the test outcome as unknown; pass/fail reporting is deferred. Consult the DesignerScript result and final accessibility report separately.
In one recorded verification, the preliminary count was 3 issues; the processed report was 40 issues (2 critical, 11 serious, 27 moderate), score 74, logged after 60 seconds. These are historical verification results, not expected counts for your application.
Find execution data and logs
Cloud build and browser session
BrowserStack Automate dashboard, matched by the full AIQ-… name.
Confirm the requested target, lifecycle and provider diagnostics. An ended session is not proof all application assertions passed.
Application pass/fail
WebDesigner playback output or AIQ execution result.
This is the application-test outcome; the provider’s accessibility test-health status can differ.
Accessibility findings
Accessibility → Automated Tests and the DS final report line.
Use processed counts and the report details, not the preliminary count.
Node operational log
Installed: <installation>/NetworkProxy/OutputLogs/ds3output0.txt. Development: distribution/OutputLogs/ds3output0.txt.
Rotates to ds3output1.txt. Configuration lines use [browser.configuration]; run lines use [browser.lifecycle].
Current redacted node configuration
GET /ds/dyn/platform/getBrowserStackConfiguration on the intended DSServer.
Shows configuration and availability without credentials.
Actual running capabilities
GET /ds/dyn/platform/getBrowserStackCapabilities?session=<DS-session>.
Returns provider session ID, browser/OS, selected connection and accessibility state.
Available target catalog / plan
AIQ Services BrowserStack account/catalog tools; provider browser-list and Plan APIs.
Catalog and account reads do not allocate browser sessions.
Operational log messages to recognize
BrowserStack configuration rejected; local browsers remain available
Invalid saved configuration; inspect fields before retrying.
Browser configuration loaded / Skipping browser with invalid configuration
Per-profile loading result.
BrowserStack accessibility build registered
Registration succeeded; includes the report build ID.
BrowserStack accessibility skipped / was not enabled by BrowserStack / build registration failed
No scans for that run; the message identifies the gate or provider failure.
BrowserStack accessibility scan failed; later failures are counted at finish
First scan failure. reason= is BrowserStack's message when the scanner answered without scanning, for example Scanner is not ready on the page after multiple retries.; cause= is a call failure. Inspect finish counts for the aggregate.
BrowserStack accessibility preliminary summary (final counts in report)
In-session summary at stop; not the processed report.
BrowserStack accessibility finished
Includes scans, failedScans and saved=true/false.
BrowserStack accessibility final report
Processed issues/severities, score, pages, components, needs-review, wait duration and report link.
BrowserStack accessibility final report not ready / is not readable with this account / report processing did not complete
Processing deadline, authorization failure or provider failure. Follow the report link.
BrowserStack remote stop acknowledged
Provider session deletion acknowledged.
BrowserStack remote stop could not be confirmed
Inspect that exact provider session in the dashboard.
BrowserStack uncertain allocation
Start response was uncertain; owned-session reconciliation/cleanup is attempted.
Failed to start browser session (operational log) / Could not start <browser>: <reason> (execution log)
The browser did not start; the run is marked failed with BrowserStack's reason, for example BROWSERSTACK_REFUSED: ….
When escalating, include the selected profile, full run name, DS/provider session IDs, actual browser/OS, relevant sanitized log lines, action that failed, and whether cleanup was confirmed. Keep access keys, tokens, private URLs containing credentials, and sensitive application data out of shared evidence.