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?
- Signing in to Level CI
- Navigate Level CI
- Setup and project configuration
- Scan options
- Quality gates
- Accessibility scan results
- Optional configuration and support
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.
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.
Note: You can access the Level CI sign-in page directly, or from the platform.
To sign in to Level CI from the platform:
Navigate to the organizational level.
Under Support, select Level CI. The Level CI sign-in page is displayed.
Enter your Email address and Password.
Select Sign In.
To access Level CI Developer Docs:
Go to Level CI Documentation. Learn more about Level CI, and access sample projects.
Navigate Level CI
Level CI includes a vertical navigation menu to help you move between Projects, Branches, Issues, and related areas more efficiently.
The navigation remains available as you move through Level CI so you can maintain context while reviewing scan results and issue activity.
You can use the navigation to:
- Move between Projects, Branches, and Issues pages
- Review scan results within a specific project or branch
- Access related pages without returning to the main dashboard
- Use breadcrumb navigation to understand your current location within Level CI
Applied filters remain visible across supported pages to help you maintain context while navigating.
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.
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.
-
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.
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.
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.
The scan will display all issues on the main branch in the issue list page.
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.
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
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.
Additionally, the details are displayed in the Level CI UI:
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 along with sample repositories to help you get started with Level CI.
Comments
0 comments
Article is closed for comments.