Using the Panel

Scan pages as you navigate, accumulate results across a workflow, inspect failing elements, and save/share reports from DevTools.

Scanning a workflow

Open the first page of the flow you want to test in Chrome.
Open DevTools (F12 / ⌥⌘I) and click the Testkase Accessibility Toolkit tab. Don't see it? Click » at the top of DevTools.
Click Full page scan. The toolkit checks the page and shows results within a few seconds.
The scan keeps recording. The status line says "Recording — keep using the site; new pages are scanned automatically".
Keep using the site. Click links, open menus, fill in forms. Each new page or new state is checked and added to the same report.

A single-page app counts too. When the page changes without a full reload — a pop-up opens, or the app moves to a new screen — that new state is checked as well.

While the panel is open, Chrome shows a bar at the top: "'Testkase Accessibility Toolkit' started debugging this browser". This is normal. The toolkit needs it to check the page. Don't click Cancel.

Pages are only recorded while a scan is running. The toolkit records pages from the moment you click Full page scan until you stop. Pages you visit with the panel just open, or after you stop, are not recorded, and you can't add them later. Start the scan first, then walk the flow.

Stopping and saving

Save report is at the top right the whole time — while recording and after you stop. If you click it while recording, the recording stops and the save window opens.
Stop scan stops recording without saving. After you stop, + New scan appears in its place.

Saving works on all pages, including modern web apps.

If a page can't be scanned

Sometimes the toolkit can't read a page. When that happens, the panel shows a message that says why, and what to do:

Chrome's own pages (chrome://…) and the Chrome Web Store can't be scanned. Chrome does not allow it.
On any other page, reload the page and try again.
If it still fails, open chrome://extensions, click Details on Testkase Accessibility Toolkit, and set Site access to On all sites.

What the panel shows

Severity counts — Critical / Serious / Moderate / Minor, added up across every page in the scan.
Pages captured — each page you went through, with its own findings.
Confirmed and Needs Review tabs — Confirmed lists problems the checker is sure about. Needs Review lists things it could not decide, which you should check yourself.
Issue list — grouped by rule. Open a rule to see details.
Inspect — click Inspect on an issue to jump to that element in the DevTools Elements tab.
Save & share — save the scan as a report and share it with your accessibility teams, right from the panel.

Saved reports in the panel

Click View reports to see the reports you saved. A saved report shows the same Confirmed and Needs Review tabs as a live scan.

The list has a link, See all scans, including Web Scanner, on the website. It opens the website, where you can see all your scans in one place.

The links in the panel's sidebar open the website:

Accessibility dashboard opens your Workflow Analyzer reports.
Website scanner opens the Website Scanner.

Differences from the web app

The toolkit and the web app use the same checking engine, at the same version, so a page checked with the same settings gives the same results in both. They reach pages differently:

Uses your live browser session — it scans whatever is rendered in your browser right now, so pages behind a login you're already signed into are in scope without configuring separate auth.
You drive the navigation — instead of submitting a fixed URL list, you click through the flow yourself and the toolkit accumulates results across the pages you visit.
Exports live in the web app — the toolkit saves reports to your workspace; the CSV summary is exported from the saved report in the web app.
Its own settings — the toolkit's WCAG version and rule toggles are set in its own Settings screen and stored in your browser. Nothing is read from your workspace defaults, and it offers no AAA levels.
Two settings you can't see — page-snapshot capture and axe's experimental rules are both on and are not exposed in the Settings screen, so a toolkit report can contain findings from experimental rules that the Website Scanner would not report.
No versions or history — a saved toolkit report is a one-off. It has a Summary tab and an All Issues tab, and nothing else: no run history, no version comparison, no consolidation with other reports. It does get a Fix plan, like a Website Scanner report.

Results flow to your workspace

Every saved toolkit report appears in the web app in two places:

Under Workflow Analyzer.
In the Website Scanner list, in the All scans and My scans tabs, next to your Website Scanner scans. The Type column says Chrome extension. See Managing scans.

Open it there to:

See the full report (summary, conformance summary, severity drill-down, per-issue detail).
Share it with accessibility teams.
Export the CSV summary.

Do not use Export as PDF on a toolkit report. The Export menu on a Workflow Analyzer report still lists Export as PDF, but there is no PDF route for analyzer reports: the button calls the Website Scanner's export with this report's id. Most of the time it fails; if that number happens to match one of your own Website Scanner scans, it quietly downloads that report instead — the wrong document, correctly branded. (It cannot reach anyone else's scan: the export checks that the scan is yours or shared with your team.) Use Export as CSV, and export a PDF from a Website Scanner report when you need one.

Saving limits

Save the report before you close DevTools. A capture is held in the panel's memory only — unlike your settings and your sign-in, it is never written to browser storage. Closing DevTools discards the whole workflow.

At most 50 pages can carry a snapshot in one save. Saving uploads the captured page HTML for every page in the workflow, and the upload request is capped at 50 pages. Go past that and the save fails outright with an error in the Save dialog — nothing is stored. Break a very long flow into two scans.

Using the Panel

On this page