Workflow Analyzer

The Workflow Analyzer scans your app in motion — not just on load. It replays a recorded user flow, captures snapshots at key interaction points, and surfaces accessibility issues that only appear after a user types, clicks, or navigates.

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 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 faster and produces a formal WCAG conformance matrix.

How it works

1. You record a flow (or upload one). The recording captures the URL path, user inputs, and interaction events.
2. TestKase replays the flow in a headless Chromium instance.
3. At each capture point in the recording, axe-core runs against the current DOM.
4. The report shows a timeline of capture points with issue counts per step.

Screenshot (TODO): Workflow analyzer timeline with issue counts per step

Running a workflow scan

1. Sidebar → Workflow Analyzer.
2. Click New Workflow (or the equivalent call-to-action).
3. Follow the on-screen steps to record or upload a flow.
4. Start the scan. Workflow scans can take a few minutes depending on the number of capture points.

Report shape

Workflow reports share the Understanding Results structure — score, severity, conformance matrix, issue list, element detail — with one extra dimension: a timeline of capture points. Each point has its own issue count, and the issue list can be filtered to a specific step.

You can:

• Jump from a timeline step to the issues it introduced.
• Compare a step's issues with the initial-load baseline to isolate what the interaction added.
• Export the full timeline + issues as PDF / CSV / JSON.

Limits

• Steps per workflow and total run time depend on your plan — see Scan limits.
• Recordings are stored in your workspace and can be re-run without re-recording.

Related

• Website Scanner
• Understanding Results
• Scan limits