Get started
Step 2 - accessibility scan

See Setup instructions for each e2e test

Continuous Accessibility does not work with the source code of your website directly, instead it requires access to your website’s running instance. There are two major options for you to configure accessibility analysis of your website: with and without end-to-end tests. The recommend option is with end-to-end which is the most flexible and cost efficient. The option without e2e tests may require ngrok subscription on your side.

During accessibility analysis of your website Continuous Accessibility e2e framework extension generates JSON report files, html files, screenshot images etc. By default those are saved into uw-a11y-reports folder.

Accessibility analysis with e2e tests

Accessibility analysis with e2e tests requires you to install corresponding e2e framework extension and to modify your tests suites in order to incorporate UserWay analysis configuration and triggers. Continuous Accessibility supports major e2e testing frameworks such as Playwright and Cypress.

Accessibility scan with Cypress

Accessibility scan with Playwright

Accessibility scan with Puppeteer

Accessibility scan with Selenium Java

Accessibility scan without e2e tests

Accessibility scan without e2e tests