Workflow Analyzer

Workflow Analyzer is the section of the web app that holds the reports the Chrome Toolkit saves. The scanning itself happens in the toolkit, inside your own Chrome browser: as you browse and interact with your app, the toolkit runs axe-core against each page you land on and accumulates the results across your navigation. When you save that capture, it appears here as a report you can open, filter, and share alongside your other scans. It also appears in the Website Scanner list, next to your Website Scanner scans, marked Chrome extension in the Type column.

Unlike the Website Scanner — which loads each URL fresh in a real Device Farm browser — a Workflow Analyzer capture records pages exactly as they were in your live session, including states you reached by typing, clicking, or navigating. That makes it the right tool for issues that only exist after interaction.

When to use it

Reach for the Workflow Analyzer when:

• The bug is behind an interaction — e.g., a form validation error state that's announced incorrectly to screen readers.
• A modal / drawer / toast opens mid-flow and needs its own conformance check.
• Focus management during navigation is what you care about.
• Accessibility regresses only after a state change (e.g., an empty-state banner appears with low-contrast text).
• The page is on an internal or private address the Website Scanner cannot reach. Because the toolkit runs in your own browser, it scans whatever your browser can already load.

For everything that can be caught on a static page load, start with the Website Scanner — it runs on real Device Farm browsers, needs no extension, and produces a formal WCAG conformance matrix.

See Toolkit vs Web App for the full capability comparison.

How a capture is produced

1. Install the Chrome Toolkit and sign in.
2. Browse your app. Drive it into whatever state you want to check — fill a form, open a modal, navigate to a sub-page. The toolkit detects each page you land on and runs axe-core against the live DOM.
3. Results accumulate per page across your session, each with its own score, severity breakdown, issue list, and an HTML snapshot.
4. Save the capture. The toolkit uploads the page snapshots and the already-computed results to your workspace, where it becomes one Workflow Analyzer report containing every page you captured.

Because the scan runs in your browser rather than on the Device Farm, a capture uses no Live or Automate minutes and needs no plan. See Scan limits.

Reviewing a capture in the web app

1. Sidebar → Workflow Analyzer.
2. Open a saved capture to see its pages.
3. Drill into any page's issues, or view the HTML snapshot with the failing element highlighted.
4. Share the capture with an accessibility team, just like a Website Scanner report.

Captures can also be deleted from here. As with a Website Scanner scan, deleting is permanent — there is no trash and no undo.

Report shape

Workflow Analyzer reports share the Understanding Results structure — score, severity breakdown, issue list, and per-element detail with HTML snippet and target selector — organized per captured page rather than per scanned URL.

You can:

• Jump from a page to the issues found on it.
• Filter the issue list by severity or rule across the whole capture.

Limits

• Captures are produced by the Chrome Toolkit only; there is no way to create or re-run one from the web app.
• The number of pages per capture is bounded by how many you navigate to in a session.
• The toolkit configures its own WCAG version and rule pack in its Settings screen — those settings live in your browser, not in your workspace, and it offers WCAG 2.0/2.1/2.2 at A or AA only (no AAA).
• Pages are unlimited; the 90-day retention window applies — see Scan limits.

Related

• Chrome Toolkit
• Toolkit vs Web App
• Website Scanner
• Understanding Results
• Scan limits