Export technical details and rule results to share with your remediation team. You can also expand risk management status sections when you need dashboard details.
On this page:
- Export selectors and code snippets from manual evaluations
- Review tested rules in scan and monitoring exports
- Find finding IDs in scan and monitoring exports
- Expand or collapse risk management status
Export selectors and code snippets from manual evaluations
Include an element's XPath or Cascading Style Sheets (CSS) selector and code snippet in a comma-separated values (CSV) export. These details help developers locate the element and review its markup without opening each finding.
Note: These fields are available only for Test Accelerator evaluations with a defined scope. They aren't available for uploaded evaluations or evaluations imported from AMP.
To include these details in an export:
- Open the manual evaluation and go to the Findings tab.
- Select the export findings button above the findings table.
- In the Export as CSV dialog, choose an option under Format columns.
- Select XPath or CSS selector and Code snippet.
- Select any other fields you'd like to include.
- Select Export.
The Format columns options determine how the selected information appears in the file:
| Option | Export output |
|---|---|
| Each as separate columns | Adds separate XPath or CSS selector and Code snippet columns for the fields you select. If a finding has no value, its cell is blank. |
| One single description column | Includes the selected values in the Description column, labeled by field name. Fields without values are omitted from the description. |
You can also use Select all or Unselect all to update your field selections. These actions include the selector and code snippet fields when they're available.
Exported values match the finding's details without truncation. Code snippets remain text rather than rendered HTML, and commas, quotation marks, and line breaks stay within the same CSV cell.
Review tested rules in scan and monitoring exports
Use the Tested rules tab in an Excel workbook (.xlsx) to review evaluated rules by status, including passed rules. This tab is available for Access Engine, axe-core, equal-access, and WAVE results.
To review tested rules:
- Export the scan or monitoring scan results as an Excel workbook (.xlsx).
- Open the downloaded workbook.
- Open the Tested rules tab.
The tab appears after the testing tool's results tab. If that results tab isn't present because all eligible rules passed, Tested rules appears after Summary. At least one eligible rule must have been evaluated for the tab to appear.
Each row represents a rule. Rows are grouped in this order: Failed, Flagged for review, and Passed. Within each group, rows are sorted by Rule Id in ascending order.
| Column | Description |
|---|---|
| Rule status | Failed, Flagged for review, or Passed. |
| Standard | Accessibility standard associated with the rule. |
| Level | Conformance level associated with the rule. |
| Errors | Reported error count for the rule. This cell is blank for Passed rules. |
| Severity | Severity associated with the rule. |
| Guideline/Summary | Guideline or summary associated with the rule. |
| Rule Title | Title of the rule. |
| Description | Description of the rule. |
| Rule Id | Identifier for the rule. |
Which rules are included?
The tab includes evaluated rules mapped to the Web Content Accessibility Guidelines (WCAG) and selected for scanning. It doesn't include:
- Non-WCAG recommendation rules.
- Rules that aren't selected for scanning.
- Info-severity rules with no failures and no ignored instances.
The Errors values for Failed rules add up to the Summary tab's Errors count. The Errors values for Flagged for review rules add up to its Warnings count. These are finding counts, not counts of rule rows.
Note: The Tested rules tab is part of scan and monitoring scan Excel exports. It isn't included in CSV, Monitoring History, or Linked Findings exports.
Find finding IDs in scan and monitoring exports
Use the Finding ID column to match exported findings to their records in the Level Access Platform.
For web scan results, this column is included in:
- Scan Excel (.xlsx) exports.
- Scan CSV exports.
- Monitoring scan Excel (.xlsx) exports.
In Excel exports, open the testing tool's findings tab and find the last column, Finding ID, after What to do. In scan CSV exports, Finding ID is also the last column. Existing columns stay in the same order.
A row can group multiple findings for the same rule on the same page. The Finding ID cell contains a list of their IDs, even when there's only one finding. For example, a row with multiple findings may contain:
["ABC-41", "ABC-42", "ABC-43"]
IDs follow the same order as the row's Selector/Xpath values and code snippets. Each ID matches the Finding ID shown in the platform. In CSV exports, the list format also helps Excel keep IDs as text rather than converting them to dates or numbers.
Note: This Finding ID column change doesn't apply to mobile scan exports or Linked Findings exports.
Expand or collapse risk management status
Risk management status sections start collapsed on the digital asset's Overview page and the workspace Dashboard. Expand them when you want to review their details.
To expand or collapse a section:
- Open the digital asset's Overview page or the workspace Dashboard.
- Find Risk management status and select the toggle button beside its heading to expand the section.
- Select the same toggle button to collapse the section again.
The workspace Dashboard also has a separate Digital assets by risk management status section. Expand or collapse it independently of the workspace's Risk management status section.
The workspace status describes the workspace as a whole. The chart shows the statuses of its individual digital assets.
Sections start collapsed again when the page reloads. Expanding or collapsing them doesn't change risk calculations, scores, status values, or the underlying data.
Note: These collapsible sections apply to the digital asset Overview and workspace Dashboard only. Risk management status on the Program Dashboard is unchanged.
Comments
0 comments
Article is closed for comments.