Workflow Analyzer

The Workflow Analyzer is where multi-page captures from the Chrome Toolkit land in the web app. As you browse and interact with your app in your own Chrome browser, the Toolkit runs axe-core against each page you land on and accumulates the results across your navigation. When you save that capture, it becomes a Workflow Analyzer report you can open, filter, and share alongside your other scans.

Unlike the Website Scanner — which loads each URL fresh in a headless browser — the Workflow Analyzer captures 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).

For everything that can be caught on a static page load, start with the Website Scanner — it's fully server-side, needs no extension, and produces a formal WCAG conformance matrix.

How it works

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 to the web app. It's stored as a Workflow Analyzer report — one entry containing every page you captured.

Screenshot (TODO): Workflow Analyzer report listing the captured pages with per-page issue counts

Reviewing a capture

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. Hide individual issues you've triaged or accepted — hidden issues are excluded from the score.
5. Share the capture with an accessibility team, just like a Website Scanner report.

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.
• Hide issues you've triaged so they no longer count against the score.

Limits

• Captures are produced by the Chrome Toolkit; the number of pages per capture is bounded by how many you navigate to in a session.
• The Free-tier page quota (10 unique pages, org-wide, lifetime) and retention windows apply — see Scan limits.

Related

• Chrome Toolkit
• Website Scanner
• Understanding Results
• Scan limits