Bug Report

Use Bug Report to convert Accessibility findings into actionable engineering work.

Bug Report turns confirmed accessibility findings into engineering work items inside the issue trackers your team already trusts. This page explains when raising a bug from a report is appropriate and how that action extends remediation beyond the dashboard into delivery rituals. Use it when you want a repeatable handoff from accessibility evidence to tracked fixes.

Typical flow

Open the report.
Review the issue or issue group.
Use the report action to create a bug.
Route it into the team's issue-management workflow.

Best use cases

confirmed issues on real user flows
high-severity findings that need engineering follow-up
tracked remediation work tied to releases or audits

Onboarding: file a bug from a report

Open All Issues and select the finding you want tracked.
Choose Report bug (or equivalent) from the row or detail actions.
Confirm the title auto-fills from the rule or element; edit so engineers recognize the user impact.
Attach screenshots or HAR if the dialog offers uploads—speeds reproduction.
Pick the integration project (Jira/Azure/etc.) if connected via Integrations; otherwise copy the deep link into your tracker manually.
After the engineering fix ships, re-run the scan and link the new build to the same ticket for closure.