Using the Issues by Page Sheet

The Issues by Page sheet displays issue count totals by page and by issue category and impact level.

PC-Only Note: It has been reported that when using Excel for Mac operating systems, the Issues by Page report may not display properly. Therefore, we recommend generating the axe Auditor Executive Report on a computer running Microsoft Office for Windows on a PC (not a Mac).

Important - About the Impact Levels: Checkpoint tests cover accessibility guidelines which can have four impact levels: Minor, Moderate, Serious, and Critical. Serious or critical impact occurs when a user encounters significant barriers or is blocked from content on the site. Minor and moderate issues aren't as serious, but still must be dealt with for the page to be considered fully compliant. Best Practice and User Agent issues are not required to be resolved to be WCAG compliant, but remediation is recommended in the spirit of digital equality.

Column Descriptions

Issues identified as a result of either Automated or Manual testing are logged so that they are associated with checkpoints, each of which is associated with issue categories. These categories include Best Practice, User Agent, and User Impact (Critical, Serious, Moderate, and Minor).

• #: The system-assigned page number, as ordered in the Test Case.
• Description: This is not to be confused with the Test Case Description, but is rather a "description" of the name of the page that was tested or is currently under test. Each page that was a part of a test run that had logged issues that were exported each appear as a separate line on this sheet. This corresponds to the Name field in the Add Page dialog box. A Page represents the individual page, component, or content within a test case that you want to test for accessibility.
• Best Practice: An accessibility issue that does not fail a WCAG Success Criteria / Checkpoint Requirement but does impact user experience is labelled a Best Practice. Many times, Best Practices are small efforts that can greatly improve the user experience.
• User Agent: An accessibility issue that is deemed to be caused by a user agent (e.g. browser or Assistive Technology) bug - not a failure to code to WCAG standards -- is considered a User Agent Issue. For example, VoiceOver does not recognize the WCAG-approved headers + ID method of marking up a complex table. It may important to document the cause and impact of a user agent issue in case a complaint is received or to alert the project owner that an alternative approach that does not trigger known user agent issues should be considered.
• Accessibility (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.
• Accessibility (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.
• Accessibility (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 issue must be resolved before a page can be considered fully compliant.
• Accessibility (Minor): This is considered an Accessibility 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.
• Total: Total numeric value counts for each page are displayed in the column for all issue categories, and for all pages in the final row.