Skip to main content

Getting Started

Introduction to Option A Diagnostics

AccessiLens is pure B2B SaaS developer diagnostic software powered by Headless Chromium and Axe-core. Before signing enterprise vendor contracts, buyers often ask for accessibility conformance evidence. AccessiLens crawls your web app out-of-band, maps failing DOM nodes to HTML/React code fixes, and exports pre-procurement scorecards — with zero JavaScript overlays and zero agency consulting lock-in.

How to

Run your first diagnostic in 3 steps

1

Open /portal?tab=diagnostic and enter your application URL (production or staging).

2

Run the $0 Baseline Check (top 15 rules) or unlock a 25-route Single-App Scan ($499 one-time).

3

Open the Evidence Hub to copy code-patch snippets or export Jira CSV, JSON, and PDF scorecards.

Why not use a JS accessibility widget?

Enterprise security and procurement teams increasingly reject overlay toolbars because runtime DOM patches do not fix underlying React/HTML source defects and may conflict with CSP policies.

Out-of-band architecture

No npm package or <script> tag is required inside your application. AccessiLens launches an isolated Chromium instance to inspect rendered views read-only.

What we intentionally do not sell

AccessiLens provides automated engineering software only. We do not sell manual screen-reader consulting retainers, human source-code fixes, or legal compliance guarantees.

Developer Quickstart

Add your web application domain in the Client Portal, trigger a baseline or multi-route crawl, and route failing WCAG rules directly into your sprint backlog.

How to

Portal scan workflow

1

Sign in at /portal/account and navigate to Apps & Diagnostics.

2

Click 'Add Application' and paste your live or staging base URL.

3

Click 'Run Diagnostic Scan' to execute Headless Chromium + Axe-core across up to 25 or 50 routes.

4

Review failing rules grouped by severity and copy the HTML/React remediation snippets.

Immediate feedback loop

After merging your fix PR, trigger Re-Scan from the portal to verify the specific Axe-core rule moved from Failed to Passed.

Zero Core Web Vitals penalty

Because diagnostics run externally against your deployed staging or production URLs, your customer-facing bundle size stays unchanged.