Using the All Issues Sheet

The All Issues sheet displays all issues exported from axe Auditor and subsequently imported into the Executive Report, which includes 13 columns of information. The information may include issues logged either automatically or as entered manually for each checkpoint. Each column allows you to take advantage of the search, sorting and filtering tools available in Microsoft Excel via the drop-down menus to the right of each column heading label. The issue data can be utilized to sort issues by various attributes in order to prioritize and organize remediation efforts.

Column Descriptions

Refer to the following descriptions to interpret each column of information displayed on the All Issues worksheet:

• Issue ID: A numeric value automatically assigned by the system when the issue was logged is displayed to uniquely identify the issue in axe Auditor.
• Page: The textual name of the page under test as entered along with the URL when the Test Case was set up.
• Summary: Typically written as a rule "must" or "should" statement, this is a brief textual description of the accessibility requirement or guideline.
• Description: This is a text field that expands on the Summary text to explain in greater detail the nature of the issue with important remediation advice.
• Impact: One of the following is displayed:
  • Critical: This issue results in blocked content for individuals with disabilities. Until a solution is implemented content will be completely inaccessible, making your organization highly vulnerable to legal action. Remediation should be a top priority.
  • Serious: This issue results in serious barriers for individuals with disabilities. Until a solution is implemented some content will be inaccessible, making your organization vulnerable to legal action. Users relying on Assistive Technology will experience significant frustration when attempting to access content. Remediation should be a priority.
  • Moderate: This issue results in some barriers for individuals with disabilities but would not prevent them from accessing fundamental elements or content. This might make your organization vulnerable to legal action. This violation must be resolved before a page can be considered fully compliant.
  • Minor: This is considered an issue that yields less impact for users than a moderate issue. For a page to be considered fully compliant this issue must be resolved but can be dealt with last.
• Issue Type: One of the following is displayed:
  • Accessibility: The issue impacts the ability for a disabled user to access content or functionality of the site. Fails the checkpoint test.
  • Best Practice: The issue impacts the ability for a disabled user to access content or functionality of the site, but does not fail the checkpoint test. This is not considered a violation.
  • User Agent: The issue is a result of the user agent interaction with the page, not necessarily the page content itself.
  • Functionality: The issue is a result of a problem with the functionality of the page and should be considered a functional defect.
  • Usability: The issue impacts the ability for all users to access content or functionality of the site.
• Notes: Additional information entered by the tester which can include remediation advice.
• User: The username of the person who logged the issue is displayed.
• Date Created: The date and time the issue was logged.
• Source Code: Source code pasted in by the tester from the page under test.
• Checkpoint: The higher-level grouping the checkpoint is associated with. These represent a further breakdown of the related WCAG Success Criteria where failures can be logically separated, typically by content type.
• Method: Either Automated or Manual is displayed to indicate the type of testing being performed when the issue was logged.