How to give WebLens access to my platform

WebLens needs two things from you to run a useful assessment: a way to reach your application, and a set of user journeys describing what your users actually do in it. This article covers access, the first half. Once that's in place, head to Writing user journeys for the second.

If your application is public

Share the URL and you're done. WebLens points its browser at the URL you give us and starts from there.

If your application requires a login

You have two options:

• A dedicated test account. Give WebLens credentials for an account scoped to whatever you want assessed. We log in before every assessment, the same way a user would. Use a read-only account where possible.
• A pre-production environment. Point WebLens at a staging URL that doesn't need credentials.

If your application sits behind SSO or IP allow-listing

The service team will help configure it. Email aps.accessibility.it@siemens.com and we'll work through SSO providers, IP allow-list ranges, or any custom auth flow.

Optional: a cookies file

For applications with non-standard session handling, you can upload a cookies file (JSON, ≤ 1MB) inside the WebLens UI. WebLens will use it on every run for that application. Useful when your test environment only accepts pre-seeded sessions.

Next

Once WebLens can reach your application, the next step is to write the journeys it should walk, Writing user journeys.