This article gives information about the appearance and details of each of the reports that are available for the Accessibility module.

Introduction¶

This article gives information about the reports for the Accessibility module.

On the Reports page, locate the Accessibility section to see the reports available for this module.

The available reports for the Accessibility module are:

• Accessibility Summary Report
• Accessibility Checks Report
• Pages with Accessibility Issues Report
• Classic Accessibility Report
• Accessibility Guidelines Report
• PDF Review Report.

1. Click Schedule This Report (calendar icon) on the same row as the report to receive the report as an email attachment. Multiple selection is allowed.
2. Click Open Report (eye icon) to get the newest report.
3. Click Report Administration (gear icon) to add other users to receive the report.

For more information, see the user guide articles:

• Report Center
• Accessibility Feature.

Navigation¶

This section gives instructions on how to navigate to the report center and how to view and receive reports.

1. Click Report Center (paper icon) on the top menu bar of Acquia Optimize.

   
2. Open Report (eye icon): Click to open the Report pane.
   • Click the link to navigate to the URL.
   • Tick the radio button to select a domain or group report.
   • Click Save.
   • A dialog box informs: Generating report. Your report is currently being generated. You will receive an email when the report is ready. You can see the current progress under the "Received reports" box to the right.
   • OK: Click to close the dialog box.
   • Open Received Reports: Click to open and view reports that are already sent.
   • The new requested report is sent to your email.

For more information about how to receive reports, see the user guide article:

• Report Center.

Accessibility Summary Report¶

The report is delivered to the email addresses for the persons assigned to receive this report.

The fields show:

• Report name, domain, and date of the scan.
• Compliance Status: Percentage of pages that meet the target compliance level.
• Pages Scanned: Pages Scanned: The total number of pages included in the scan.
• Pages with Issues: The number of pages with accessibility issues.
• Unique Snippets with Issues: The total number of unique snippets with issues that the scan found.
• Level A Compliance: The number of checks in this level that the scan considered, the number of checks that passed, and the number of checks that need to be fixed.
  • Errors: The issue is in direct conflict with the standard and needs to be fixed. These are usually content issues such as HTML snippets that are not compliant. These issues can only be fixed with a change to the source code.
    • The number of checks that failed.
    • The number of snippets with issues.
  • Warnings: The issue is most likely in conflict with the standard, do a manual review and fix the issue.
    • The number of checks that failed.
    • The number of snippets with issues.
  • Needs Review: The issue cannot be programatically determined as an error or warning and requires human review. Do a manual review of the issue to determine if any fix can be done.
    • The number of checks that failed.
    • The number of snippets with issues.
• Level AA Compliance: The number of checks in this level that the scan considered, the number of checks that passed, and the number of checks that need to be fixed.
  • Errors: The issue is in direct conflict with the standard and needs to be fixed. These are usually content issues such as HTML snippets that are not compliant. These issues can only be fixed with a change to the source code.
    • The number of checks that failed.
    • The number of snippets with issues.
  • Warnings: The issue is most likely in conflict with the standard, do a manual review and fix the issue.
    • The number of checks that failed.
    • The number of snippets with issues.
  • Needs Review: The issue cannot be programatically determined as an error or warning and requires human review. Do a manual review of the issue to determine if any fix can be done.
    • The number of checks that failed.
    • The number of snippets with issues.
• Level AAA Compliance: The number of checks in this level that the scan considered, the number of checks that passed, and the number of checks that need to be fixed.
  • Errors: The issue is in direct conflict with the standard and needs to be fixed. These are usually content issues such as HTML snippets that are not compliant. These issues can only be fixed with a change to the source code.
    • The number of checks that failed.
    • The number of snippets with issues.
  • Warnings: The issue is most likely in conflict with the standard, do a manual review and fix the issue.
    • The number of checks that failed.
    • The number of snippets with issues.
  • Needs Review: The issue cannot be programatically determined as an error or warning and requires human review. Do a manual review of the issue to determine if any fix can be done.
    • The number of checks that failed.
    • The number of snippets with issues.

For more information, see the user guide articles:

• Report Center
• Accessibility Feature.

Accessibility Checks Report¶

The report is delivered to the email addresses for the persons assigned to receive this report.

The fields show:

• Report name, domain, and date of the scan.
• Compliance Status: Percentage of pages that meet the target compliance level.
• Pages Scanned: Pages Scanned: The total number of pages included in the scan.
• Pages with Issues: The number of pages where the scan found accessibility issues.
• Errors: This section of the report has the columns:
  • Check: This column lists the name of the check that failed.
  • Responsibility: This column lists the most common party within your organization who should have the competencies needed to repair the error.
  • Guideline: This columns lists the WCAG guideline that the check falls under.
  • Issue: This column lists the number of times this issue occurs.
  • Pages: This column lists the number of pages that contain this issue.

For more information, see the user guide articles:

• Report Center
• Accessibility Feature
• Accessibility Checks.

Pages with Accessibility Issues Report¶

The report is delivered to the email addresses for the persons assigned to receive this report.

The fields show:

• Report name, domain, and date of the scan.
• Compliance Status: Percentage of pages that meet the target compliance level.
• Pages Scanned: Pages Scanned: The total number of pages included in the scan.
• Pages with Issues: The number of pages where the scan found accessibility issues.
• Unique snippets with issues: The number of snippets in which the scan found accessibility issues.

• Errors: This section shows information about the errors that the scan found. This section of the report has the columns:
  ​

  
  • Page: This column shows the page header and a link to the page with the issue.
  • Failing checks count: This column lists the number of failing checks found on the page.
  • Snippets with issues: This column shows the number of snippets on the page that have issues.

• Warnings: This section shows information about serious issues that the scan found. This section of the report has the columns:
  ​

  
  • Page: This column shows the page header and a link to the page with the issue.
  • Failing checks count: This column lists the number of failing checks found on the page.
  • Snippets with issues: This column shows the number of snippets on the page that have issues.

• Review: This section shows information about issues that need to be reviewed by a human. This section of the report has the columns:

  
  • Page: This column shows the page header and a link to the page with the issue.
  • Failing checks count: This column lists the number of failing checks found on the page.
  • Snippets with issues: This column shows the number of snippets on the page that have issues.

For more information, see the user guide articles:

• Report Center
• Accessibility Feature.

Classic Accessibility Report¶

The report is delivered to the email addresses for the persons assigned to receive this report.

• Report Overview: This shows the total number of issues and progress made to fix them in a quick overview of the compliance level that was selected during the scan setup. The fields shown are:
  • Report name and domain name
  • Date of the scan.
  • The fields in the Report Overview section show:
    • Total number of accessibility issues found
      • The number of issues
      • The number of unique issues and affected pages.
      • The overall accessibility compliance scale, that gives the total number of issues that are done and the number of issues that need to be reviewed.
    • The graph on the right side of the Overview section shows:
      • Date of the last 5 scans
      • Issues completed at the time of each scan.
• Level A Compliance: This section shows the number of issues and the number of affected pages, as well as:
  • The number of issues done in this level of compliance
  • The number of issues that remain in this level of compliance
  • The number of issues of each type:
    • Errors
    • Warnings
    • Needs Review.
• Level AA Compliance: This section shows the number of issues and the number of affected pages, as well as:
  • The number of issues done in this level of compliance
  • The number of issues that remain in this level of compliance
  • The number of issues of each type:
    • Errors
    • Warnings
    • Needs Review.
• Level AAA Compliance: This section shows the number of issues and the number of affected pages, as well as:
  • The number of issues done in this level of compliance
  • The number of issues that remain in this level of compliance
  • The number of issues of each type:
    • Errors
    • Warnings
    • Needs Review.
• All Level A Accessibility Issues
  • Success Criteria: The name and description of the success criteria that there are issues for.
  • Part of Guideline: The WCAG guideline that this criteria falls under
  • Classification:
    • Error
    • Warning
    • Review.
  • Pages: The number of affected pages.
• All Level AA Accessibility Issues
  • Success Criteria: The name and description of the success criteria with issues.
  • Part of Guideline: The WCAG guideline that this criteria falls under.
  • Classification:
    • Error
    • Warning
    • Review.
  • Pages: The number of affected pages.
• All Level AAA Accessibility Issues
  • Success Criteria: The name and description of the success criteria with issues.
  • Part of Guideline: The WCAG guideline that this criteria falls under.
  • Classification, sorted for severity:
    • Error
    • Warning
    • Review.
  • Pages: The number of affected pages.

For more information, see the user guide articles:

• Report Center
• Accessibility Feature.

Accessibility Guidelines Report¶

The report is delivered to the email addresses for the persons assigned to receive this report.

The fields show:

• Report name, domain, and date of the scan.
• Compliance Status: Percentage of pages that meet the target compliance level.
• Crawl Information:
  • Pages Scanned: Pages Scanned: The total number of pages included in the scan.
  • Pages with Issues: The number of pages where the scan found accessibility issues.
  • Unique snippets with issues: The number of snippets in which the scan found accessibility issues.
  • Total locations affected: The total number of pages, documents, and other locations where the scan found issues.
• Criteria for issues: This header shows the level of compliance. In this example, the user has selected the highest level of compliance, WCAG 2.2 (Level AAA) v2. The report has the columns:
  • WCAG guideline: Part of Guideline: The WCAG guideline that this criteria falls under.
  • The name of the WCAG guideline.
  • Unique Snippets with issues: This column shows the number snippets with issues within this guideline, sorted for severity:
    • Error
    • Warning
    • Review.
  • Total Locations Being Affected: This column shows the number of locations with issues within this guideline, sorted for severity:
    • Error
    • Warning
    • Review.

For more information, see the user guide articles:

• Report Center
• Accessibility Feature
• Accessibility Checks.

PDF Review Report¶

The report is delivered to the email addresses for the persons assigned to receive this report.

The fields show:

• Report name, domain, and date of the scan.
• PDFs scanned: The number of PDF files that the scan included.
• PDFs Pending Review: This shows the PDFs that are in the review process.
• URL: This column lists the URL for the PDF files that are in the review process.

For more information, see the user guide articles:

• Report Center
• Accessibility Feature
• Scan PDF files for Accessibility Issues
• Clarity PDF Remediation.

Additional Resources¶

For more information, see the User Guide articles:

• Accessibility Feature: How to set up and use the Accessibility feature.
• Report Center: How to set up and receive reports.
• Priority, Severity, Difficulty, and Likelihood: Information about how Acquia Optimize determines the severity of issues.