--- title: "Accessibility Issues by page" date: "2026-03-23T12:02:00+00:00" summary: image: type: "page" url: "/web-governance/accessibility-issues-page" id: "cfc501cd-44ff-43e6-9d66-41e1f23a2234" --- 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 ------------ This option on the left menu in Acquia Web Governance Accessibility displays accessibility issues according to the page where they occur. Navigation ---------- Select **Issues by page** from the left menu. The following tabs are available: You can take the following actions on this page: * **Search**: Search for specific issue names. * **Filter**: Filter for the following: * Level * Role * Labels * Severity * **Edit columns**: Choose to show or hide table colums. * **Export**: Export the current view in .csv format. The table displays the following information: * **Page**: The page name, click the link to navigate to the page view for a list of all issues on the page. * **URL**: The URL for the page, click the link to view the page on the internet. * **Page views (30 days)**: The number of views the page has received in the past 30 days. * **Issues**: The number of accessibility issues on the page. * **Labels**: All labels applied to the page. Click the + icon to add a label. * **Open in**: On the same row as a page, click **Extension** to open the page in the Web Governance Browser Extension. For more information, visit [Handle accessibility issues with the browser extension](/node/61691). Handle issues by page --------------------- This section provides instructions on how to view and handle failling accessibilty 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_ 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. ### 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 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.