Switch to Access Engine

On this page:

• Check whether your project uses Access Engine
• Switch your project to Access Engine
• Review accessibility issues generated by Access Engine
• Validate fixes with a new scan

Level CI now runs accessibility scans using Access Engine. If you run accessibility scans in CI pipelines, you will see updated issue data and additional metadata in Level CI results.
When your project uses Access Engine, accessibility issues in Level CI include:

• Unified rule identifiers
• WCAG success criteria references
• Remediation guidance
• Code snippets and selectors to help locate issues

This update aligns Level CI issue data with the rules and findings used across other Level Access tools.

Check whether your project uses Access Engine

When you open a project in Level CI, the interface indicates whether your scans run on the legacy engine or Access Engine.
If your project still uses the legacy engine, Level CI displays:

• A New Access Engine is live banner on the Project List page.

  

• Warning indicators next to projects using the legacy engine.

  

• An Action required banner on Issue List and Branch List pages.

  

Branches that still run on the legacy engine are labeled Legacy Engine.

Follow the instructions in the interface to switch your project to Access Engine.

Switch your project to Access Engine

If your project still uses the legacy engine, Level CI guides you through the transition.

To switch your project:

1. Open your project in Level CI.
2. Locate the Action required banner on the Issue List or Branch List page.
3. Open the Notification Drawer from the banner.
4. Follow the steps provided for your ALM configuration.
5. Complete the required updates to move your project to Access Engine.

Once the switch is complete, the main branch of your project runs scans using Access Engine.

Review accessibility issues generated by Access Engine

After your project switches to Access Engine, all new scans generate accessibility issues using the Access Engine rule set.

When you open an issue in Level CI, the issue drawer provides detailed information including:

• ruleId → ruleKey = access-engine-<ruleId>

• title → Issue title

• description → Rule explanation

• whatToDo → How to fix section

• whyItMatters → Why it matters section

• successCriteria → WCAG Info section with links to W3C Understanding docs

• severity → Severity badge (INFO, LOW, HIGH, CRITICAL)

• New derived fields computed during ingestion:

  • Code Snippet (codeSnippet)

  • CSS Selector (cssSelector)

  • Path Selector (pathSelector)

• Issue drawer updates:

  • New WCAG Info tab for success criteria.

  • New “Why it matters” tab/section for explanatory content.

  • Updated layout based on Figma designs.

Validate fixes with a new scan

After you update your code:

1. Commit and push your changes.
2. Allow your CI pipeline to run a new Level CI scan.
3. Review the scan results in Level CI.
   • If the issue is resolved, it no longer appears in the scan results.
4. All new scans for your project continue to run using Access Engine.