--- title: "How to review an accessibility issue" date: "2024-10-24T15:33:46+00:00" summary: "Learn how to review and address accessibility issues on your website." image: type: "page" url: "/web-governance/how-review-accessibility-issue" id: "d6b2394e-d436-4363-8f32-755f8cee73f1" --- Table of contents will be added Introduction ------------ This article provides instructions on how to review or ignore an accessibility issue. You can do a review on warning and review issue types. The difference between warning and review type checks is the likelihood that the code snippet contains an accessibility barrier is higher in a warning. The issue types are as follows: * **Errors** (insect icon) These are content issues such as HTML snippets that are not compliant. These issues can only be fixed with a change to the source code. * **Warnings (bell icon)** Warnings are often actual accessibility barriers. These issues need to be reviewed manually. * **Reviews (eye icon)** Reviews are generic issues that cannot be tested by the software and therefore need to be reviewed manually.  Note With Reviews, “Mark as Fixed” should only be used if the code snippet has been repaired on the HTML for the page. If it is not fixed properly, the line of code is re-flagged on the next scan. If it is not possible or necessary to repair the issue in the code, mark the issue as “Review” instead. ### Identify issue types with the web browser extension Locate issues that need a review with the web browser extension. 1. Open the website and activate the web browser extension. The extension toolbar opens. 2. Click **Content Issues** (the insect icon). ![The location of the Content Issues button on the extension toolbar.](https://acquia.widen.net/content/5cf9b0ae-f577-414a-b4d1-810adf098443/web/Mon_Opt_WebBrowserExtension-Toolbar-ContentIssuesButton.png) 3. On the _Content Issues_ page, locate the _Accessibility_ section.   ![The Accessibility section of the Content Issues page in the web browser extension.](https://acquia.widen.net/content/3e4e7b50-9910-4a1e-82eb-270ed7dd46e8/web/Mon_Extension-ContentIssues-AccessibilitySection.png) 4. On the same row as a failing check, click **See Issues**. ![Monsido Web Browser Extension](https://acquia.widen.net/content/6b6efbaa-c299-4ceb-853f-2bb4ca135ca3/web/Mon_Extension-ContentIssues-SeeIssuesButton.png) 5. The details pane opens. Issues have an icon to the left of the issue name, to indicate the type of issue. For more information, visit [Web browser extension](/node/58711/). ### Identify issue types with the accessibility feature Locate issues that need a review with the accessibility feature. 1. Click **Accessibility** (icon of a human with arms outstretched) on the domain dashboard toolbar to open the _Accessibility_ dashboard. ![The location of the Accessibility button on the domain toolbar.](https://acquia.widen.net/content/79462b58-cd9b-4a6a-a404-8a111c48805e/web/Mon_Opt_Dashboard-Accessibility.png) 2. Select **Pages with Failing Checks** from the menu on the left side of the page. The list shows the URLs for pages that have accessibility issues. ![The Pages with Failing Checks option in the left menu on the Accessibility dashboard. The menu items are described in the document text.](https://acquia.widen.net/content/a2048703-c496-4c5a-8eb9-7703f74af666/web/Mon_Opt_Accessibility-LeftMenu-PagesWithfailingChecks.png) 3. Click **Open Page Details** (the page icon) on the same row as a page in the list. ![The location of the Open Page Details button on the same row as an issue.](https://acquia.widen.net/content/989515e9-43ab-49c7-866b-2b659e6d4e36/web/Mon_Opt_Accessibility-PagesWithFailingChecks-OpenPageDetails.png) 4. Click on a check in the list to open the details panel to the right of the list. Issues have an icon to the left of the issue name, to indicate the type of issue. For more information, visit [How to use the Accessibility feature](/node/61661/)​. How to manually review an issue ------------------------------- Issues with a Warning or Review icon need to be manually reviewed. These issues cannot be tested by the software and therefore need to be reviewed manually. This section gives instructions on how to manually identify and review an issue. ### How to manually review an Issue with the web browser extension 1. Click to select an issue in the web browser extension list. 2. The issue page opens in the extension. 3. Click to expand the **Accessibility Help Center** button. ![The location of the Accessibility Help Center button for an issue on the web browser extension.](https://acquia.widen.net/content/b3f56be4-9ea8-407b-b0ef-f24e3a32acef/web/Mon_WebBrowserExtension-ContentIssues-AccessibilityHelpCenterButton.png) In some cases, there is a link to **Read More in Help Center**. This the new accessibility help center article, which gives more detailed descriptions of the issues and steps to repair them. ![The location of the Read More help center link for an issue on the web browser extension.](https://acquia.widen.net/content/ac703b52-2280-4777-878d-82dcf94c0510/web/Mon_WebBrowserExtension-ReadMoreInHelpCenterLink.png) 4. Read the instructions for the issue and review the issue manually to ensure that it is compliant. If you cannot find information here about your accessibility issue, visit [The help article for my check is missing](/node/59696/). 5. If needed, follow the steps given in the help center to repair the issue. For more information, visit [Web browser extension](/node/58711/). ### How to manually review an issue with the accessibility feature 1. Click **Pages with failing checks** from the menu on the left side of the Accessibility page. ![The Pages with Failing Checks option in the left menu on the Accessibility dashboard. The menu items are described in the document text.](https://acquia.widen.net/content/a2048703-c496-4c5a-8eb9-7703f74af666/web/Mon_Opt_Accessibility-LeftMenu-PagesWithfailingChecks.png) 2. Click **Open Page Details (the page icon)**: On the same row as a page with failing checks. ![The location of the Open Page Details button on the same row as an issue.](https://acquia.widen.net/content/989515e9-43ab-49c7-866b-2b659e6d4e36/web/Mon_Opt_Accessibility-PagesWithFailingChecks-OpenPageDetails.png) 3. Click **Accessibility Help Center** (graduation cap icon) on the same row as a URL in the list to navigate to the Accessibility Help Center and read more about the error and how to fix it. 4. Read the instructions for the issue and review the issue manually to ensure that it is compliant. 5. If needed, follow the steps given in the help center to repair the issue. 6. Click **Mark as Fixed** when the issue is repaired. Note “Mark as Fixed” should only be used if the code snippet has been repaired on the HTML for the page. If it is not fixed properly, the line of code is re-flagged on the next scan. For more information, visit [How to use the Accessibility feature](/node/61661/)​. How to set an issue to reviewed ------------------------------- After you review an issue and determine cannot or does not need to be fixed, you can set the issue to _Reviewed_. 1. Select **Pages with Failing Checks** from the menu on the left side of the Accessibility page. ![The Pages with Failing Checks option in the left menu on the Accessibility dashboard. The menu items are described in the document text.](https://acquia.widen.net/content/a2048703-c496-4c5a-8eb9-7703f74af666/web/Mon_Opt_Accessibility-LeftMenu-PagesWithfailingChecks.png) 2. Click **Open Page Details (the page icon)**: On the same row as a page with failing checks. 3. ![The location of the Open Page Details button on the same row as an issue.](https://acquia.widen.net/content/989515e9-43ab-49c7-866b-2b659e6d4e36/web/Mon_Opt_Accessibility-PagesWithFailingChecks-OpenPageDetails.png) 4. Click to select an issue with a Warning (bell icon) or Review (eye icon) type from the list on the left. The pane on the right side of the page provides more information about the issue. 5. Click **Reviewed** to set the issue to _Reviewed_ status. Note Use this option if it is not possible or necessary to repair the issue in the code. For more information, visit [How to use the Accessibility feature](/node/61661/)​. #### When to review all issues Use the **Review All Issues** option only when you are sure that every issue in the list is the same issue, and only if it is not possible or necessary to repair the issue in the HTML code. How to mark an issue as fixed ----------------------------- After you review an issue and determine that it does need to be fixed, you must first follow the instructions and fix the issue and then you can select **Mark as Fixed**. When using Reviews, “Mark as Fixed” should only be used if the code snippet has been repaired on the HTML for the page. If it is not fixed properly, the line of code is re-flagged on the next scan. 1. Select **Pages with Failing Checks** from the menu on the left side of the Accessibility page. ![The Pages with Failing Checks option in the left menu on the Accessibility dashboard. The menu items are described in the document text.](https://acquia.widen.net/content/a2048703-c496-4c5a-8eb9-7703f74af666/web/Mon_Opt_Accessibility-LeftMenu-PagesWithfailingChecks.png) 2. Click **Open Page Details (the page icon)**: On the same row as a page with failing checks. ![The location of the Open Page Details button on the same row as an issue.](https://acquia.widen.net/content/989515e9-43ab-49c7-866b-2b659e6d4e36/web/Mon_Opt_Accessibility-PagesWithFailingChecks-OpenPageDetails.png) 3. Click to select a Warning (bell icon) or Review (eye icon) issue from the list on the left. The pane on the right side of the page provides more information about the issue. 4. Fix the issue in the HTML code. 5. Click **Mark Check as Fixed** after the issue is fixed in the HTML code of the page. Note When you are working with Reviews, “Mark as Fixed” should only be used if the code snippet has been repaired on the HTML for the page.