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
The Acquia Web Governance scan of your website presents you with a comprehensive list of accessibility issues. These fall into two main categories:
Automated checks: These are programmatically found issues.
Assisted checks: These are potential issues that require human verification.
Whether it is a missing alt attribute or a contrast warning, it is critical that you evaluate and prioritize these steps as a part of your remediation process. To help you manage your workflow effectively, Web Governance offers several decision actions that you can apply to flagged issues.
The following sections provide a breakdown of the available accessibility decisions and describe how they impact your compliance results.
Use this option if the failing check is not applicable to your specific context. For instance, if you know that your entire website does not feature any multimedia, you can ignore any multimedia-related checks to keep your list clean.
Ignore check
This action ignores the entire check (the rule itself) completely.
This action targets a specific instance of an issue, and does not turn off an entire rule.
Note
For Automated checks (errors): When you mark an automated check as Ignored, it acts as a temporary all-clear. It tells the system that the issue has been addressed. During the next automated scan, the platform will verify the fix. If the code is still broken, the issue will automatically resurface in your reports.
For Assisted checks (warnings and reviews): When you mark an assistive check as Ignored, it is a permanent action. Because these issues require human context or manual review and cannot be programmatically verified by a scanner, the system trusts your judgment and will not flag that specific snippet again.
Local ignore: Use this option from the Web Governance Browser Extension or the page details view to ignore the code snippet on that specific page.
Global Ignore (Fast track): When you ignore a code snippet from the Automated checks tab in the Fast track view, that specific snippet is ignored globally across your entire site.
Important
You cannot bulk-ignore all instances of a specific check on a single page (for example, you cannot click one button to ignore all "missing alt text" images on the homepage). You must either ignore the check entirely, ignore specific code snippets one-by-one on that page, or use Fast track to ignore a specific snippet across the domain.
View ignored checks
Navigate to Issues by type.
Select the Ignored checks tab.
For instructions on how to ignore code snippets in bulk and how to restore ignored checks and snippets, visit How to ignore an accessibility check.
When an issue is resolved, you can update its status to reflect the work.The system handles automated errors and assistive checks differently as follows:
For Automated Checks (Errors): Mark an automated check as fixed for a temporary all-clear. This action tells the system the issue has been addressed. During the next automated scan, the platform will verify the fix. If the code is still broken, the issue will automatically resurface in your reports.
For assisted checks (warnings and reviews): Mark assisted checks as fixed for a permanent action. Because these issues require human context or manual review and cannot be programmatically verified by a scanner, the system trusts your judgment and will not flag that specific snippet again.
Not all flags are guaranteed errors. Assisted checks require a human to verify them before they are sent to the development queue.
Confirm as Issue: This option is used primarily in the manual testing flow for assisted checks. When you mark a check as Confirmed, a distinct badge is applied to the code snippet. This badge acts as a visual confirmation for your team to signal, "Yes, a human has reviewed this warning and confirmed it is a legitimate accessibility barrier that needs to be fixed."
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
The Acquia Web Governance scan of your website presents you with a comprehensive list of accessibility issues. These fall into two main categories:
Automated checks: These are programmatically found issues.
Assisted checks: These are potential issues that require human verification.
Whether it is a missing alt attribute or a contrast warning, it is critical that you evaluate and prioritize these steps as a part of your remediation process. To help you manage your workflow effectively, Web Governance offers several decision actions that you can apply to flagged issues.
The following sections provide a breakdown of the available accessibility decisions and describe how they impact your compliance results.
Use this option if the failing check is not applicable to your specific context. For instance, if you know that your entire website does not feature any multimedia, you can ignore any multimedia-related checks to keep your list clean.
Ignore check
This action ignores the entire check (the rule itself) completely.
This action targets a specific instance of an issue, and does not turn off an entire rule.
Note
For Automated checks (errors): When you mark an automated check as Ignored, it acts as a temporary all-clear. It tells the system that the issue has been addressed. During the next automated scan, the platform will verify the fix. If the code is still broken, the issue will automatically resurface in your reports.
For Assisted checks (warnings and reviews): When you mark an assistive check as Ignored, it is a permanent action. Because these issues require human context or manual review and cannot be programmatically verified by a scanner, the system trusts your judgment and will not flag that specific snippet again.
Local ignore: Use this option from the Web Governance Browser Extension or the page details view to ignore the code snippet on that specific page.
Global Ignore (Fast track): When you ignore a code snippet from the Automated checks tab in the Fast track view, that specific snippet is ignored globally across your entire site.
Important
You cannot bulk-ignore all instances of a specific check on a single page (for example, you cannot click one button to ignore all "missing alt text" images on the homepage). You must either ignore the check entirely, ignore specific code snippets one-by-one on that page, or use Fast track to ignore a specific snippet across the domain.
View ignored checks
Navigate to Issues by type.
Select the Ignored checks tab.
For instructions on how to ignore code snippets in bulk and how to restore ignored checks and snippets, visit How to ignore an accessibility check.
When an issue is resolved, you can update its status to reflect the work.The system handles automated errors and assistive checks differently as follows:
For Automated Checks (Errors): Mark an automated check as fixed for a temporary all-clear. This action tells the system the issue has been addressed. During the next automated scan, the platform will verify the fix. If the code is still broken, the issue will automatically resurface in your reports.
For assisted checks (warnings and reviews): Mark assisted checks as fixed for a permanent action. Because these issues require human context or manual review and cannot be programmatically verified by a scanner, the system trusts your judgment and will not flag that specific snippet again.
Not all flags are guaranteed errors. Assisted checks require a human to verify them before they are sent to the development queue.
Confirm as Issue: This option is used primarily in the manual testing flow for assisted checks. When you mark a check as Confirmed, a distinct badge is applied to the code snippet. This badge acts as a visual confirmation for your team to signal, "Yes, a human has reviewed this warning and confirmed it is a legitimate accessibility barrier that needs to be fixed."
Web Governance