Reporting Feature
Introduction
AAArdvark provides a nifty reporting feature for users to take stock of the scan details on the workspace and site. These reports are available as PDF or xlsx (spreadsheet) files to summarize scans, issues, issue instances, and WCAG compliance.
Running a Scan
The reporting feature requires a scan to be run before presenting itself as an option. If you haven’t already, feel free to Run an Automated Scan.
After allowing the scan to run on the site, the options to download the reports should be made visible in the Site Dashboard.
Downloading the Report
To download a report, click the PDF or xlsx buttons below the site information on the site’s dashboard. This should appear just by the Site Statistics, under the site scan details as a button.
After clicking either button, you will be notified that the report is being generated. Give it a few minutes to complete. Once it’s done, the button will say, “PDF/Excel file is ready to download.” Click it again to download the report from your browser.
Information Included Within Reports
The information included in the reporting features varies depending on which file was downloaded.
PDF File Report
Information about the site is included in the PDF file, such as the open issues currently active on the site, the pages scanned, and a graph depicting the issues count history.
If there have been any previous scans, a history of all the scans performed on the site will also be listed in table format. The date, number of pages, errors, warnings, and total active issues found at the time of the scan are marked.
Following that, any failing WCAG guidelines are outlined with the success criteria, the title, and the passes/failed. A list of the most problematic pages can also be viewed, along with the number of active instances.
To top it off, a summary of the list of active issues can be viewed.
xlsx Report File
The downloadable spreadsheet will allow users to view the Issue ID, who the issue is assigned to, what level of WCAG the issue applies to, and the principle. The success criteria are also listed, followed by details depicting the message and failure for that particular issue.
The suggested technique for handling that issue is included, along with its severity and active instances. Depending on whether the issue was found in an automated scan or manual audit, it will also be noted in a column, along with its active status.
