Article Navigation
When to Review All Issues
Introduction
This article gives instructions on how to review or ignore an accessibility issue.
Reviews can be done on warning and review issue types. The difference between warning and review type checks is the likelihood of the code snippet containing an accessibility barrier.
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.
Open the website and activate the web browser extension. The extension toolbar opens.
Click Content Issues (the insect icon).
On the Content Issues page, locate the Accessibility section.
On the same row as a failing check, click See Issues.
The details pane opens. Issues have an icon to the left of the issue name, to indicate the type of issue.
For more information, see the user guide article:
Identify Issue Types with the Accessibility Feature
Locate issues that need a review with the Accessibility feature.
Click Accessibility (icon of a human with arms outstretched) on the domain dashboard toolbar to open the Accessibility dashboard.
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.
Click Open Page Details (the page icon) on the same row as a page in the list.
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, see the user guide article:
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
Click to select an issue in the web browser extension list.
The issue page opens in the extension.
Click to expand the Accessibility Help Center button.
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.
Read the instructions for the issue and review the issue manually to ensure that it is compliant.
If needed, follow the steps given in the help center to repair the issue.
For more information, see the user guide article:
How to Manually Review an Issue with the Accessibility Feature
Click Pages with Failing Checks from the menu on the left side of the page.
Click Open Page Details (the page icon): On the same row as a page with failing checks.
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.
Read the instructions for the issue and review the issue manually to ensure that it is compliant.
If needed, follow the steps given in the help center to repair the issue.
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, see the user guide article:
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.
In the Accessibility feature:
Click Pages with Failing Checks from the menu on the left side of the page.
Click Open Page Details (the page icon): On the same row as a page with failing checks.
The Page Details page opens.
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 shows more information about the issue.
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, see the user guide article:
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.
In the Accessibility feature:
Click Pages with Failing Checks from the menu on the left side of the page.
Click Open Page Details (the page icon): On the same row as a page with failing checks.
The Page Details page opens.
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 shows more information about the issue.
Fix the issue in the HTML code.
Click Mark Check as Fixed after the issue is fixed in the HTML code of the page.
Note: When using Reviews, “Mark as Fixed” should only be used if the code snippet has been repaired on the HTML for the page.
For more information, see the user guide article:
Additional Resources
For more information, see the user guide articles:
For definitions and explanations of the acronyms and abbreviations used, see:
For further assistance, contact the support team or use the chat and help features inside the application.