--- title: "How to use Limited Access Accessibility" date: "2026-04-01T13:07:47+00:00" summary: image: type: "page" url: "/web-governance/how-use-limited-access-accessibility" id: "f372c056-36ac-4315-b5fc-3db442ca77e5" --- Table of contents will be added Note These steps explain the process in the new navigation. If you are not subscribed to the Web Governance Limited Access program, these steps may differ from your view. Contact support to join the Limited Access program. All customers will automatically receive the update after the general rollout. All new customers automatically receive this version. Introduction ------------ Web Governance Accessibility checks are done by the scan. There are two types of accessibility checks: * **Automated**: This category contains failed checks as determined by the scan. Issues of this type are confirmed errors that must be fixed. * **Assisted**: This category contains checks that the program was unable to verify. Issues of this type are potential errors, and a human must make the final evaluation. This document provides instructions on how to find and repair accessibility issues with Acquia Web Governance. Navigate to Web Governance Accessibility ---------------------------------------- 1. From the domain overview, select the domain you want to work with. 2. Select **Accessibility** (an icon of a human with outstretched arms) on the domain menu bar. For information about navigational options within Accessibility, visit [Accessibility navigation](/node/96481). Locate accessibility issues --------------------------- You can locate issues in several ways. Choose the view that is best for your method of working from the left menu. * **Summary page**: This is the Accessibility dashboard. Use the links provided to navigate to the list of all failing checks for the domain. * **Issues by type**: Select this option from the left menu. This view displays failing checks arranged by type of issue. * **Issues by page**: Select this option from the left menu. This view displays failing checks arranged by the website page they occur on. * **Fast track**: Select this option from the left menu. This view displays failing checks in the HTML code for the domain. * **PDFs**: Select this option from the left menu. This view lists the PDF files that the scan found on your site and provides information about remediation. If you include links to external PDFs on your domain, you can view the accessibility status of those. For more infomation, visit [Accessibility navigation](/node/96481). Issues by type -------------- * This method lets you view failing accessibility checks by the type of issue. View issues per: **Automated checks**: These are accessibility checks that the scan is able to accurately identified as failing. * **Assisted checks**: These are accessibility checks that cannot be determined by the scan and need a human review. * **Ignored checks**: These are the failing checks that have been marked **Ignore** by a user. The scan does not consider these checks. Visit [Accessibility: Issues by type](/web-governance/accessibility-issues-type "Accessibility: Issues by type") for full instructions on how to fix automated and assisted checks with the _Issues by type_ method Issues by page -------------- This method lets you view failing accessibility checks by the page they occur on. Visit [Accessibility issues by page](/node/96596) for full instructions on how to fix automated and assisted checks with the _Issues by page_ method. Fast track ---------- This feature lets you view failling accessibilty checks by code, with the option to handle them individually or in bulk. For full instructions, visit: * [Accessibility Fast track navigation](/node/96601) * [How to use Accessibility Fast track](/node/86141) Restore an ignored check ------------------------ On the _Issues by type_ and the _Issues by page_ pages, select the **Ignored checks** tab above the list. Click **Actions** on the same row as the ignored check that you want to restore and select **Restore this check**. Only Admin users can restore an ignored check. For full instructions, visit [How can I unignore an accessibility issue?](/node/86056) Accessibility guide ------------------- The Web Governance Accessibility guide provides guidelines on WCAG 2.0 and some common 2.1 requirements. To navigate to the accessibility guide and view all of the available articles, visit [Accessibility Guide](/node/58376). For more information, visit [About the accessibility guide](/node/58696). History Center -------------- The History Center stores all accessibility issues and details from previous scans. For more information, visit [Accessibility history](/node/86066). Accessibility compliance score ------------------------------ The compliance score for the accessibility checks is calculated by using 100 (a perfect score) minus the number of errors found. This is then divided by the total number of accessibility checks. For example: If the compliance for individual accessibility checks is calculated by the: **total number of pages minus pages with issues** for the: **check total number of pages multiplied by 100** The system calculates the _number of pages that fail the check_ as opposed to the total number of pages, regardless of the number of issues. Accessibility reports --------------------- The available reports for Web Governance Accessibility 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** (a 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** (an eye icon) to get the newest report. 3. Click **Report administration** (a gear icon) to add other users to receive the report. For more information, visit [Accessibility reports](/node/58701). Additional resources -------------------- For information on how to configure Web Governance Accessibility, visit [Accessibility setup instructions](/node/61656).