Integrations (JIRA / Slack)

Accessibility reporting often needs to move beyond the dashboard into issue tracking and team collaboration workflows.

This guide explains when to use shared platform integrations alongside Accessibility reporting and how they fit into remediation workflows such as ticketing and team notifications. It focuses on how those capabilities support accessibility outcomes rather than duplicating full integration setup documentation elsewhere.

Common integration scenarios

create engineering tickets from report findings
share report outcomes with QA or product teams
connect Accessibility triage to an existing bug-management workflow

Important note

Many integrations are shared platform capabilities. This page exists to explain how they are used in the Accessibility context rather than to duplicate full integration setup docs.

Onboarding: wire Jira or Slack for Accessibility

Complete the global integration setup first—see Jira Integration or Slack Integration for credentials, OAuth, and workspace allowlists.
In the Accessibility report or workspace settings (exact menu depends on UI version), choose the integration you want to receive new issues or notifications.
Map severity or tags to Jira priorities if the UI offers mapping; otherwise agree a default priority in your triage playbook.
Send a test ticket from a non-production report to confirm fields populate correctly.
Train reviewers to use Bug Report for one-off escalations versus integration rules for systematic routing.