Collaboration

Accessibility testing is rarely a one-person job — a designer finds the issue, a developer fixes it, QA verifies, and compliance signs off. TestKase Accessibility supports that loop through three primitives:

1. Accessibility Teams — named groups inside your org, admin-managed.
2. Sharing Scans — share individual reports with one or more teams; inline comments for discussion.
3. Notifications — email or in-app alerts when scans complete, are shared with you, or receive comments.

All three are scoped to your organization — scans and teams don't cross org boundaries.

Typical workflow

1. An admin creates the accessibility teams (e.g., "Frontend", "QA", "Compliance").
2. A scan creator runs a scan and shares it with the relevant team(s).
3. Team members open the report, comment on specific issues, and re-scan after fixes.
4. Notifications close the loop — the creator sees comments, assignees see shared reports.

Permissions at a glance

• Team creation & membership — org admins and owners.
• Share a scan — the scan's creator (or any member of a team the scan is already shared with).
• View a shared scan — any member of a team the scan has been shared with.
• Delete a scan — the scan's creator, or an org admin / owner.