Level Access Continuum Explorer Retirement — when and how should I migrate?

Existing Level Access customers need a change-awareness card on the Continuum Explorer retirement and the migration path to supported tooling so audit evidence and developer testing workflows do not break in 2026.

Replace Continuum Explorer with the Level Access browser extension unless you also need auditable scan history and reports; only then move evidence capture into the Platform.

Blockers

Who this is for

Candidates

Replace Continuum Explorer with the Level Access browser extension

As of 2026-03-19, Continuum Explorer's retirement has already occurred: official support ended on 2024-05-31, it stopped receiving Access Engine updates after that date, and it was retired and removed from the Chrome Web Store on 2024-06-07. Level Access's official replacement is the Level Access browser extension for Chrome. The replacement keeps the core browser-based workflow for single-page scans, iframe scanning, manual-review findings, and highlight-in-page inspection, while adding support for WCAG 2.2. Official docs do not publish public self-serve pricing for this extension; check official docs and your Level Access contract.

When to choose

Use this when your main need is a direct developer-workflow replacement for Continuum Explorer in 2026. It is the decisive choice when engineers need supported local, pre-production, protected-page, or dynamic-flow testing without staying on an unsupported extension.

Tradeoffs

Closest workflow match to Continuum Explorer and officially supported, but it does not automatically retest when the page changes, does not preserve Continuum Explorer's 1-10 severity model, and does not keep Continuum Explorer's in-extension sorting by severity, noticeability, and tractability.

Cautions

If teams rely on exported evidence, note the migration caveat: Continuum Explorer could download results directly as .json, while the Level Access browser extension requires sending results to the platform before downloading them as .xlsx or .csv. The browser extension is documented as Chrome-compatible, and platform-connected result sending is limited to Accelerate and Enterprise customers.

Sources

Move evidence capture into the Level Access Platform with browser-extension and platform scans

As of 2026-03-19, the durable supported path for saved scan evidence is the Level Access Platform rather than Continuum Explorer itself. The browser extension can send scan results to the platform, and platform docs separate on-demand scans from scheduled monitoring for ongoing evidence, trend comparison, remediation validation, and automated flow testing. Platform docs also show package-gated capabilities: sending extension results to the platform is for Accelerate and Enterprise customers, while scan and monitoring limits vary by Essentials, Accelerate, and Enterprise. Official docs name these packages but do not publish public pricing numbers; check official docs and your contract.

When to choose

Use this when the blocker is not just developer testing, but preserving auditable scan history, exported reports, and repeatable remediation validation in 2026. It is the decisive choice when unsupported local-only extension output would break compliance evidence or team reporting workflows.

Tradeoffs

Gives stronger evidence retention and richer reporting than a browser-only workflow, but it introduces package dependency and platform setup. Some functionality differs from AMP, and page limits are finite per scan and per monitoring configuration.

Cautions

Do not assume a one-for-one export path from Continuum Explorer. The official comparison says the browser extension's downloadable results come only after sending results to the platform, and the file formats change from Continuum Explorer's .json to platform-oriented .xlsx and .csv. Platform docs also distinguish one-time scans from recurring monitoring, so teams should map old ad hoc workflows to the correct mode before audit periods.

Sources

Facts updated: 2026-03-19
Published: 2026-04-03

Related questions

Try with your AI agent

$ npm install -g pocketlantern
$ pocketlantern init
# Restart Claude Code, Cursor, or your MCP client, then ask:
# "Level Access Continuum Explorer Retirement — when and how should I migrate?"
Missing something? Request coverage