Overview

Level CI does not analyze your website’s source code directly. Instead, it requires access to a running instance of your website.

There are two main ways to configure an accessibility analysis:

• With End-to-End (E2E) Tests
  • This is the recommended, most flexible and cost-efficient approach.
• Without E2E Tests
  • This option may require a tunneling solution such as ngrok if your site is running locally.

Output from Level CI

When Level CI performs an accessibility analysis, it generates several types of files, including JSON reports.

By default, these files are saved to the folder:

level-ci-reports/

Accessibility analysis with E2E tests

Using E2E tests for accessibility analysis requires:

1. Installing the Level CI package for your chosen E2E framework.
2. Modifying your test suites to incorporate Level CI analysis configuration and triggers.

Level CI supports major E2E frameworks:

• Cypress
• Playwright
• Puppeteer
• Selenium (Java)

Setup Guides

• Accessibility Scan with Cypress
• Accessibility Scan with Playwright
• Accessibility Scan with Puppeteer
• Accessibility Scan with Selenium Java

Accessibility Analysis Without E2E Tests

Level CI can also perform accessibility scans without E2E tests following these guidelines:

• Requires access to a running website instance.
• May need ngrok or a similar tunneling service if scanning local environments.
• Setup is simpler but less flexible, with limited CI/CD automation.
• Accessibility Scan Without E2E Tests