Skip to main content

About Level CI

Level CI is a developer-first accessibility automation tool from Level Access that brings accessibility testing directly into your development workflow.

On this page

What's Level CI?

Level CI brings accessibility testing directly into your CI/CD pipelines—helping your team identify and fix issues before deployment. By integrating seamlessly with your development workflow, it ensures your product remains compliant with accessibility standards while reducing risk.

With Level CI, your organization can maintain high accessibility standards, streamline compliance efforts, and build more inclusive digital experiences from the start.

Screenshot of the projects page in the Level CI interface.

Signing in to Level CI

Before you can sign in, you must register your account to obtain login credentials. Registration is by invitation and happens during onboarding. Send an email to onboarding@levelaccess.com and your Customer Success Manager. 

To access Level CI: 

  1. Go to Level CI.

  2. Enter your Email address and Password. 

  3. Select Sign In. 

To access Level CI Developer Docs: 

Setup and project configuration

Start by adding your project to the Level CI dashboard. You can import from platforms like GitHub, Bitbucket, GitLab, or Azure DevOps. Manual project setup is also available, if you are using any other CI tool.

Screenshot of the project creation page, displaying a list of available repositories.

Once added, you can configure the following:

  • Project name: Use a clear, lowercase format.
  • PR comments and widget configuration : Toggle PR decoration and widget configuration.
  • Main branch: Define the default branch for analysis.
  • Quality gate: An automated checkpoint that verifies accessibility standards based on set thresholds and severity levels, providing pass or fail results. If not selected, it defaults to the organization's standard.
  • URL Parameters: Activate URL Parameters to detect URLs with query parameters and hashes in the sitemap.
  • Dynamic URLs: You can set up URL templates for dynamic pages to ensure full coverage.

For more information on initial set-up for ALM please refer to developer docs below:

Scan options

Level CI supports scans with E2E testing frameworks and scans without any E2E tests managed by Level CI infrastructure.

  • Level CI supports accessibility scanning within popular end-to-end (E2E) testing frameworks. Detailed setup guides are available for each supported framework in our developer documentation.

  • Scans without E2E testing frameworks: Level CI allows you to configure the connection to your live website and specify the exact page paths you want to scan. The accessibility analysis is then executed entirely on Level CI’s infrastructure, providing comprehensive insights without requiring any setup on your end. 

    For details on scans without e2e tests, refer to Scans with no e2e tests.

Quality gates

Quality gates act as your accessibility checkpoints throughout the development process. They help enforce your standards by automatically approving or blocking code based on scan results.
Level CI lets you define your own rules for what should pass or fail—whether that’s zero critical issues, no new violations, or custom thresholds for each severity level.

Screenshot of the quality gates page, it lists the accessibility thresholds for Level CI projects.

When a gate is triggered:

  • Pull requests can be flagged or blocked
  • Contributors receive immediate, actionable feedback
  • Teams can remediate issues before merging

Quality gates help you shift accessibility left—catching issues early and maintaining consistency as your product evolves.

Accessibility scan results

The first analysis is automatically triggered on your project’s default branch, typically called main or master.

The analysis results will display according to the defined quality gate thresholds and will include status of scan, severity of accessibility issues and details of all issues.

The results of the first scan will be visible in the CLI, build (if set-up) and the Level CI interface.

Screenshot of the branch summary page, listing the quality results based on set thresholds, E2E testing framework and status.

The scan will display all issues on the main branch in the issue list page.

Screenshot of the issue list page, displaying a list of accessibility issues detected by Level CI.

A detailed view of each issue is available showcasing the issue details, affected code snippet, affected accessibility aspects and a How to fix tab to fix the issue.

Screenshot of the detailed issue view, showing a description, code snippet, and suggested fixes for accessibility issues.

Going forward, the tool will automatically trigger a new analysis every time you make changes to the main branch, whether it’s through:

  • Direct pushes
  • Pull request merges
  • Branch merges

Workflow Overview

  • Commit and push: Make changes to your code and push them to the repository.
  • Review check status: Monitor the status of your changes to ensure everything is processed correctly.
  • Troubleshoot: If there are issues, review the logs and resolve any problems.
  • Review analysis results: Once the analysis is complete, review the results to identify any potential issues or areas for improvement.
  • Adjust the accessibility quality gate: Modify the A11y Quality Gate if needed to improve the overall accessibility quality of your code.
  • Optionally re-run the analysis: If you’ve made changes or fixes based on the analysis, you can re-run the analysis to verify the improvements.

To enable this, a one-time setup is required in your repository settings. Your team’s designated developer/dev-ops engineer can complete the integration.

You can set-up additional pull request analysis which will display quality gate results as pull request decoration. A peer-reviewer and the developer can then work together to remediate the issues.

Key benefits of setting up accessibility quality gates at branch level include:

  • Branch-level testing for early detection.
  • Enforced quality gates to prevent new issues.
  • Custom compliance criteria that reflect your team’s goals.
Screenshot of the Quality Gate page with analysis results displayed in a table.

Additionally, the details are displayed in the Level CI UI:

Screenshot of the PR summary page with the quality gate results.

Optional configuration and support

For teams looking to tailor the experience, optional settings include:

  • Custom report settings (e.g., screenshots, visual aids)
  • Support for TypeScript
  • Excluding reports from version control

For details on optional configuration and support, refer to the troubleshooting guide.

Powered by Zendesk