Product

Workflow.

Raw findings dedupe into fix surfaces — durable remediation units that persist across scans. Templates fix once; content gets routed to the right owner; site-wide issues stop appearing on every page.

Workflow states

1. Open — surface created, not yet assigned.
2. In progress — assigned to a developer or content manager with optional due date.
3. Fix applied — work shipped, awaiting verification.
4. Ready for rescan — queued for the next scan or a verification run.
5. Completed — verified resolved.

Why it's faster than per-page triage

A template issue that affects 200 pages becomes one fix surface, not 200 tickets. The developer fixes the template; verification confirms the resolution propagates. A site-wide issue (missing landmarks, missing html-lang) shows reach percentage so you know how universal the impact is.

Roles built in

Each user sees the work they own — content managers see content-class surfaces, developers see template- and site-class surfaces, and agency admins see across the portfolio. SLA configs and assignment metadata attach to each surface for accountability.