General Information
You can hide errors in the Eye-Able Audit and Report once they have been manually reviewed by you. This ensures that they are not issues affecting the accessibility of the page. The rules for hiding errors are always bound to the domain and must be individually set for other domains and subdomains.
Warnings and hints (marked in yellow or white) are generally intended for manual review. Successfully reviewed issues can be hidden using the hide function. Additionally, for warnings and notes, you can completely deactivate a review step for a domain.
Even for errors, there might be exceptional cases of false positives or instances where manual review indicates minimal impact on page accessibility. However, errors cannot be generally deactivated; only individual errors can be hidden. The only exception is the text contrast error, provided a contrast mode is available on the website.
Impact on the Report
Errors hidden in the audit will be taken into account in the next iteration of the report for your domain. These issues will no longer be considered in the regular evaluation.
Synchronization within the Organization
Hidden issues will also apply to all your colleagues. The list of hidden issues is regularly retrieved from the Eye-Able server. You can also manually trigger an update of this list using the "Synchronize" button in the "Audit" interface.
Usage in Audit
In Audit, there is a new button for each issue to hide the error.
After clicking the button, a popup opens. In this popup, you confirm the successful review of the issue. You can also set the review step to be completely deactivated for this domain. This option is only available for warnings and notes.
After confirmation, hidden issues will appear in a separate section of the "Audit" interface during the next check.
Here, you can interact with issues as usual. Using the same button that initially hid an issue, you can make it visible again in this section. Pay attention to whether a single issue or the entire review step was hidden. Reverting a hidden issue may reveal many more issues. You can distinguish these by the popup text.
Usage in Report and Dashboard
A feature for hiding issues and managing current hiding rules will soon be added to the dashboard.
Potential Issues
Hiding issues is based on the HTML of each problem. Changes to classes, attributes, or textual content can cause previously hidden errors to reappear. Dynamically generated attributes such as timestamps, classes, or IDs may also prevent certain elements from being hidden.
If you and a colleague observe different behaviors in Audit, ensure that the page is in the same state (e.g., login or cookie banner) and the browser versions are as similar as possible.
For questions or issues, please contact our support.