---
title: "Accessibility reports"
date: "2024-03-05T14:05:14+00:00"
summary: "Explore accessibility reports: summary, checks, issues, guidelines, and PDF review. Improve web compliance and user experience."
image:
type: "page"
url: "/web-governance/accessibility-reports"
id: "2013c3a2-cb1f-4e85-a0a5-348cb5d8f01e"
---

Table of contents will be added

Introduction
------------

This article provides information about the appearance and details of each of the reports that are available for Web Governance Accessibility.

On the _Reports_ page, locate the _Accessibility_ section to see the list of reports available.

![The Report Center landing page. The fields are described in the document text.](https://acquia.widen.net/content/8isoqjldpj/web/Mon_ReportCenter-Dashboard.png?w=720&v=3776d6a3-0efc-4263-bc32-e0e036749b97&itok=l0ak4YQt)

The available reports for Web Governance Accessibility are:

*   Accessibility Summary
*   Accessibility Issues by Type
*   Accessibility Issues by Page
*   Accessibility Guidelines
*   PDF Review
*   **Schedule This Report**: Click the calendar icon on the same row as the report to receive the report as an email attachment. Multiple selection is allowed.
*   **Open Report**: Click the eye icon on the same row as the report to get the newest report.
*   **Report Administration**: Click the gear icon n the same row as the report to assign this report to other users.

Navigation
----------

This section provides 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.
    
    ![The location of the Report Center button on the domain toolbar.](https://acquia.widen.net/content/p11ocrjvkb/web/WebGov_MainToolbar-ReportCenterButton.png?w=720&v=492f348a-e458-4b3e-af13-557c7b1c71e5&itok=CIxA0QwO)
    
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.

Accessibility Summary report
----------------------------

The report is delivered to the email addresses of all of the people who are assigned to receive this report.

![An example of an Accessibility Checks report](https://acquia.widen.net/content/sl2vwhm5eu/web/WebGov_ReportCenter-AccessibilitySummaryReport.png?w=720&v=8c75129a-45fa-4de3-a39d-9886d0c7d1b2&itok=mm2HhtoW)

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 determined by the programming 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 determined by the programming 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 determined by the programming 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.

Accessibility Issues by Type report
-----------------------------------

The report is delivered to the email addresses of all of the people who are assigned to receive this report.

![The Accessibility Checks report, the fields in the report are described in the document text.](https://acquia.widen.net/content/83mkmrm3sr/web/WebGov_ReportCenter-AccessibilityChecksReport.png?w=720&v=c0d2f4e7-ce5a-4697-a89f-cd137c1f0de4&itok=vUVfLx9g)

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.

Accessibility Issues by Page report
-----------------------------------

The report is delivered to the email addresses of all of the people who are 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.

Accessibility guidelines report
-------------------------------

The report is delivered to the email addresses of all of the people who are assigned to receive this report.

![An example of an Accessibility Guidelines report](https://acquia.widen.net/content/hk2gvacown/web/WebGov_ReportCenter-AccessibilityGuidelinesReport.png?v=c8efb545-f4b0-47e1-a1e4-783516538b33)

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

PDF Review report
-----------------

The report is delivered to the email addresses of all of the people who are 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.

Additional resources
--------------------

For more information, visit:

*   [How to use the Report Center](/node/61286)
*   [How to use the Accessibility feature](/node/61661)