Exporting & Sharing Reports

Use this page to understand how Accessibility results can be shared across stakeholders and exported for downstream workflows.

The following sections outline common reasons teams export Accessibility results and which downstream workflows those exports support. They also explain how sharing reflects the active state of the report you are viewing, including filters and visibility choices.

Common use cases

sharing findings with engineering or QA
sending audit evidence to accessibility stakeholders
reviewing results outside the dashboard
exporting the current report state after filters or hide/restore decisions

Important behavior

Report exports reflect the active issue state for the current report view. In scheduled aggregated reporting, historical consistency can still limit how past aggregate views are reflected.

How to export (onboarding)

Open the report from Navigating the Dashboard.
Apply any filters or hide/restore decisions first—exports represent the current visible state.
Use the report’s export or share action (label varies by surface) and pick the format your stakeholder needs (spreadsheet, PDF, or packaged evidence where offered).
Store exports with build metadata (date, commit SHA, scan type) so audit trails stay traceable.
For recurring programs, pair exports with Integrations so issues also land in Jira or Slack automatically.