Audit Results and Run History
Every audit execution creates a versioned run. Open View Runs from an audit URL to review the history without replacing the evidence from earlier executions.
Run history
The history lists the run date, status, Accessibility, Performance, Best Practices, and SEO scores, duration, and a details action. Opening a version loads the strategy, scores, findings, and evidence recorded for that run.
Use separate runs to answer questions such as:
- Did the accessibility score improve after a release?
- Did a fix remove the original failed finding?
- Did the selected Web, Mobile, or Desktop strategy change?
- Did a previously completed URL begin failing to analyze?
Completed report
The report header identifies the URL, plan, start time, run version, strategy, and accessibility score. Summary cards show the total, passed, failed, manual, and not-applicable result counts.
Finding groups may include:
- the rule and explanation;
- the affected CSS selector and HTML snippet;
- a screenshot when the analysis produced one; and
- related WCAG guidance.
Manual findings require human verification. A passed automated check also does not prove that the whole user experience is accessible.
Refine a failed finding with AI
Select Refine with AI on a failed finding to request:
- a clearer description of the problem;
- a suggested remediation; and
- WCAG and verification guidance.
The request uses an Accessibility fix credit. The result may be reused for the same finding, but it is still a recommendation. Review the suggested code in context, test it safely, and rerun both automated and relevant manual checks.
Create an issue
Use the finding's issue action to send the context into RabbitQA's shared issue flow. Depending on the workspace integrations, the issue can be managed in RabbitQA or passed to a connected tracker. See Issue Tracker for the module-level view.
