Self-Hosted Scans

User Set-up

End-to-End (E2E) tests and Continuous Integration/Continuous Deployment (CI/CD) pipelines configured.

Example

A React.js website is built and deployed using Bitbucket Pipelines and tested with Cypress for E2E testing.

The A11y (Accessibility) scan: is executed entirely within the user’s pipeline infrastructure, providing full control and flexibility.

This approach is the most flexible and cost-efficient for users, as it allows them to manage the entire testing and scanning process within their existing infrastructure.

Managed Scans

User Setup

CI/CD Infrastructure Without E2E Tests

In this setup, the user has a CI/CD pipeline in place but does not have End-to-End (E2E) tests.

Example

A React.js website developed using a Git repository, with the A11y (Accessibility) scan triggered through the user’s CI/CD pipeline.

Pros

  • A11y scan execution on UserWay infrastructure: The scan is carried out on UserWay’s infrastructure, offloading processing from the user’s own environment.
  • Scans websites launched on local development environments: The ability to scan websites that are not publicly available, such as those hosted on local dev environments.
  • Supports intranet-only sites: It can scan internal sites that are restricted to intranet access.
  • Seamless integration with CI/CD pipelines: The A11y scan is triggered directly within the CI/CD pipeline, ensuring accessibility checks are automated within the deployment flow.

Cons

  • Less flexibility compared to E2E tests: Without E2E tests in place, the scanning process is more rigid, offering fewer customization options for testing.
  • Additional costs: The user will incur charges for:
    • CI/CD pipeline runtime for triggering and executing the scan.
    • UserWay infrastructure runtime for processing the scan.
    • HTTP tunnel traffic for accessing and scanning websites hosted on internal or restricted environments.