TestKase
TestKase
|Docs
Accessibility TestingCollaboration

Collaboration

Accessibility teams, shared scans, and notifications.

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 so everyone works from the same report.
  3. Notifications — email alerts when your scan finishes or fails, and when you're added to or removed from a team.

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 shared report, review the findings, and fix them in their own tools.
  4. The scan's creator re-scans after fixes to confirm the report is clean.

Permissions at a glance

  • Team creation, rename, deletion & membership — org owners and admins only.
  • Share / unshare a scan — the scan's creator only, and only with teams the creator belongs to.
  • View a shared scan — any member of a team the scan has been shared with. Except the page snapshots: element inspection is creator-only, so a shared viewer reads the issue detail without the snapshot.
  • Re-run or edit a scan — the scan's creator only (the API returns 403 for everyone else).
  • Delete a scan — the scan's creator only. Org admins and owners cannot delete someone else's scan.
  • Read the History tab — any member of a team the scan is shared with, same as viewing.
  • Consolidate — any member of a team the scan is shared with; the scan can go into their combined report. Compare is the scan's creator only.
  • Delete a run from a scan's History — the scan's creator only, and never the first (base) run.
  • Hide an issue — the scan's creator only, and only through the API. See Hiding an issue.

There are no public links: everything above requires a signed-in TestKase account in the same organization. See Sharing scans.