Access Continuum

Access Continuum is an SDK for adding automated accessibility checks to software tests. It is best suited to developer teams embedding checks in CI workflows, particularly across web and mobile projects. Its appeal is the range of ways to integrate testing; its main drawback is reliance on Level Access services and repositories.

Overview

Continuum is designed to catch accessibility issues before code reaches a live environment. Teams can target code snippets, page nodes, or fully rendered pages, making it possible to fit checks into different stages of an automated test suite. It includes the Professional edition of Access Engine and defaults to automatic tests that do not require human validation.

That makes routine checks practical, but it does not eliminate the need for human judgment. Guided Automatics can flag suspicious items for review, while advisory tests are not run in Continuum. Teams should treat it as an automated layer in an accessibility process, not a complete replacement for manual assessment.

Key features

Flexible test authoring and integration

An XML-based scripting framework lets teams author accessibility tests even if they do not already use a test framework or automation setup. That is a useful entry point for teams building their process, while existing test suites can draw on sample projects for xUnit, Cucumber, Selenium, TestNG, JUnit, Jasmine, Karma, Jest, Playwright, WebdriverIO, Robot Framework, and Appium. The breadth gives teams multiple integration paths, though it also means the best fit depends on how their current tests are structured.

Setup instructions cover SDKs for C#, Java, JavaScript, and Python; Ruby is also named among supported package-repository languages. The product page names integrations including iOS, Android, Appium, Cucumber, Python, Karma, Jasmine, Java, Ruby, and Sauce Labs. Web and mobile examples, including Appium projects for Android and iOS, make its cross-platform intent concrete.

Test coverage and results

Continuum supports WCAG 2.1 and offers automated scans, manual review tools, mobile testing, CI/CD integration, and remediation guidance. Results can be returned as JSON for use in a workflow or exported in a UI format to the Accessibility Management Platform (AMP). This gives teams a choice between consuming output in their own tooling and handling it in AMP.

The dependency is significant: Continuum relies on AMP services for best-practice accessibility data, and installation requires access to Level Access package repositories such as dl.levelaccess.net, npm.levelaccess.net, and nuget.levelaccess.net. Network access may also be needed for AMP. Organizations with restrictions on external services or package sources should resolve that dependency before choosing it.

Licensed customers receive personalized training and expert support for customizing scripts, which can help teams adapt the framework to their workflows. Continuum is made by Level Access, founded in 1999; the company states that it is ISO 27001 certified and that its platform has completed a SOC 2 Type II audit.

Pricing

Access Continuum is a paid, licensed product with custom pricing. Teams should request a quote to assess fit against their budgets; no free plan, trial length, seat allowance, or usage quota is provided for Continuum.

Platforms

Continuum is listed for Android, iOS, Linux, macOS, web, and Windows, as well as API use. Its sample projects and integrations span web and mobile testing, with Appium examples for Android and iOS. This breadth suits teams covering several environments, but platform support alone does not remove the AMP and package-repository requirements.

Who it's for

Continuum is a strong candidate for developers who want accessibility checks inside continuous integration and automated tests, especially teams working across web and mobile. Its scripting framework can also serve teams without an existing test harness. It is a less natural choice for organizations seeking a standalone checker, avoiding external service dependencies, or needing a public price before engaging with a vendor.

Pros and cons

• Pros: Tests can target snippets, page nodes, or rendered pages, so teams can place checks where they are most useful.
• Pros: XML scripting and sample projects for many frameworks offer paths for both new and established automation setups.
• Pros: JSON output and AMP export accommodate both custom workflows and a dedicated results interface.
• Cons: AMP services and Level Access package repositories are required, which can complicate adoption in restricted environments.
• Cons: Guided Automatics may still need human review, and advisory tests are not run in Continuum.
• Cons: Custom pricing requires a demo request, making budget comparison less direct.

Alternatives

Accessibility Testing Software is the broader category for comparing tools. Consider WAVE if a freemium option is preferable; it also offers a paid API subscription starting at $10 a month with a 250-credit minimum purchase.

Alfa is worth considering for teams seeking a free, open-source option distributed as separate npm packages. Axe Developer Hub has a free tier with one API key for open-source projects or solo developers, plus a free trial for its paid offering.

IBM Equal Access Accessibility Checker is a free, open-source alternative with browser extensions and CI/CD and automated-testing packages. Axe DevTools offers a free extension limited to one page at a time, making it a possible fit for that narrower use.

Evinced may suit teams wanting to evaluate a paid product through a free trial; its Site Scanner trial lasts 14 days and requires no credit card. axe-core is a free, open-source accessibility testing engine. axe Auditor is another paid option for Android, iOS, macOS, web, and Windows.

Verdict

Choose Access Continuum if your developer team wants to embed accessibility checks across automated web and mobile tests and can work with AMP and Level Access repositories. Its adaptable scripting, framework examples, and flexible result handling are the clearest reasons to choose it. Look elsewhere if those dependencies are impractical or if you need transparent pricing before starting a vendor conversation.