--- title: "How to use Web Governance Accessibility - Limited Access" date: "2026-03-30T09:54:26+00:00" summary: image: type: "page" url: "/web-governance/how-use-web-governance-accessibility-limited-access" id: "6c6e5a87-0675-495e-92ab-5af019c9a224" ---         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. Introduction ------------ Acquia 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 Web Governance Accessibility. Navigation ---------- 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. * **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 information, visit [Accessibility navigation](/node/96481). Issues by type -------------- This section provides instructions on how to view and handle failling accessibilty checks by type of check. ### Fix automated checks This category contains the failed checks found by the scan. Issues of this type are confirmed errors that must be fixed. 1. From the left menu, select **Issues by type**. 2. Select the **Automated checks** tab. 3. Click on a failing automated check. 4. Fix the issue in the HTML code.  Web Governance includes the Accessibility Guide, a series of documents that provide a deep dive into each check. In the corresponding Accessibility Guide article for the check, you can find information about why it is important and how to fix it. The link to the Accessibility Guide article that corresponds to the failing check is at the top of the page. 5. To view the issue on the page, select **Extension** on the same row as an issue. 6. After the issue is fixed, use the kebab menu on the same row as the issue and select one of the following options: * **Mark as fixed on this page**: Use this option when the error is fixed. This removes the error from the results list for the page. If the issue is not fixed properly, it is flagged again on the next scan. * **Mark as fixed on all pages**: Use this option when the error is fixed on all pages of the domain. This removes the error from the results list for the page. If the issue is not fixed properly, it is flagged again on the next scan. * **Ignore on this page**: Use this option when you are sure that the check is incorrectly flagged or cannot be fixed. This option instructs the scanner to ignore the check on this page. * **Ignore on all pages**: Use this option when you are sure that the check is incorrectly flagged or cannot be fixed. This option instructs the scanner to ignore the check for all pages of the domain. 7. Start a new scan and repeat the steps above to verify that you have sufficiently fixed the issues. For more information, visit [Accessibiliy: Issues by type](/node/96591). Note Use the _Ignore_ options only if you are sure that the marked issue is not an error or if it cannot be fixed. Your compliance score adjusts accordingly. Evaluate the issue thoroughly before you instruct the scan to ignore it. ### Fix assisted checks 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. 1. From the left menu, select **Issues by type**. 2. Select the **Assisted checks** tab. 3. Click on a failing assisted check. 4. Review the issue. For more infornation, visit [How to review an accessibility issue](/node/59486). 5. Fix the issue in the HTML code.  Web Governance includes the Accessibility Guide, a series of documents that provide a deep dive into each check. In the corresponding Accessibility Guide article for the check, you can find information about why it is important and how to fix it. The link to the Accessibility Guide article that corresponds to the failing check is at the top of the page. 6. To view the issue on the page with the Web Governance Browser Extension, select **Extension** on the same row as an issue. 7. Use the kebab menu on the same row as the issue and select one of the following options: * **Mark as fixed on this page**: Use this option when the error is fixed. This issue will not be flagged again for this page by subsequent scans. * **Mark as fixed on all pages**: Use this option when the error is fixed on all pages of the domain. This issue will not be flagged again for pages on this domain on subsequent scans. * **Ignore on this page**: Use this option when you are sure that the check is incorrectly flagged or cannot be fixed. This tells the scanner to ignore the check on this page. * **Ignore on all pages**: Use this option when you are sure that the check is incorrectly flagged or cannot be fixed. This tells the scanner to ignore the check on all pages of the domain. 8. Start a new scan and repeat the steps above to verify that you have sufficiently fixed the issues. Note Use the _Ignore_ options only if you are sure that the marked issue is not an error or if it cannot be fixed. Your compliance score adjusts accordingly. Evaluate the issue thoroughly before you instruct the scan to ignore it. Issues by page -------------- This section provides instructions on how to view and handle failing accessibility checks by page. ### Fix automated checks This category contains the failed checks found by the scan. Issues of this type are confirmed errors that must be fixed. 1. From the left menu, select **Issues by page**. 2. Select the **Automated checks** tab. 3. Click on a failing automated check. 4. Fix the issue in the HTML code.  Web Governance includes the Accessibility Guide, a series of documents that provide a deep dive into each check. In the corresponding Accessibility Guide article for the check, you can find information about why it is important and how to fix it. The link to the Accessibility Guide article that corresponds to the failing check is at the top of the page. 5. To view the issue on the page, select **Extension** on the same row as an issue. 6. After the issue is fixed, use the kebab menu on the same row as the issue and select one of the following options: * **Mark as fixed on this page**: Use this option when the error is fixed. This removes the error from the results list for the page. If the issue is not fixed properly, it is flagged again on the next scan. * **Ignore on this page**: Use this option when you are sure that the check is incorrectly flagged or cannot be fixed. This option instructs the scanner to ignore the check on this page. * **Open in extension**: Select this option to view the issue in the Web Governance Browser Extension. 7. Start a new scan and repeat the steps above to verify that you have sufficiently fixed the issues. Note Use the _Ignore_ options only if you are sure that the marked issue is not an error or if it cannot be fixed. Your compliance score adjusts accordingly. Evaluate the issue thoroughly before you instruct the scan to ignore it. For more information, visit [Accessibility: Issues by page](/node/96596). ### Fix assisted checks 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 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. 1. From the left menu, select **Issues by page**. 2. Select the **Assisted checks** tab. 3. Click on a failing assisted check. 4. Review the issue. For more information, visit [How to review an accessibility issue](/node/59486). 5. Fix the issue in the HTML code.  Web Governance includes the Accessibility Guide, a series of documents that provide a deep dive into each check. In the corresponding Accessibility Guide article for the check, you can find information about why it is important and how to fix it. The link to the Accessibility Guide article that corresponds to the failing check is at the top of the page. 6. To view the issue on the page with the Web Governance Browser Extension, select **Extension** on the same row as an issue. 7. Use the kebab menu on the same row as the issue and select one of the following options: * **Mark as fixed on this page**: Use this option when the error is fixed. This issue will not be flagged again for this page by subsequent scans. * **Ignore on this page**: Use this option when you are sure that the check is incorrectly flagged or cannot be fixed. This tells the scanner to ignore the check on this page. * **Open in extension**: Select this option to view the issue in the Web Governance Browser Extension. 8. Start a new scan and repeat the steps above to verify that the issues are not flagged by the scan. Note Use the _Ignore_ option only if you are sure that the marked issue is not an error or if it cannot be fixed. Your compliance score adjusts accordingly. Evaluate the issue thoroughly before you instruct the scan to ignore it. Fast track ---------- This feature lets you view failing accessibility 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 ------------------------ Admin users can restore an ignored check. This section provides instructions. 1. On the _Issues by type_ and the _Issues by page_ pages, select the **Ignored checks** tab above the list. 2. Click **Actions** on the same row as the ignored check that you want to restore and select **Restore this 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 * 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. * Click **Open report** (an eye icon) to get the newest report. * Click **Report administration** (a gear icon) to add other users to receive the report. For more information, visit [Accessibility reports](https://docs.acquia.com/node/58701). Additional resources -------------------- For information on how to configure Web Governance Accessibility, visit [Accessibility setup instructions](/node/61656).