These steps explain the process in the new navigation. If you are not subscribed to the Web Governance Early Access program, these steps may differ from your view. Contact support to join the Early Access program. All customers will automatically receive the update after the general rollout.
Introduction
The Fast track option on the left menu in Acquia Web Governance Accessibility displays accessibility issues according to the code snippets on the pages where they occur.
Fast track locates elements such as links, images, and text and addresses any accessibility and data privacy issues that are found. You can repair issues in bulk and fix, review, and ignore HTML snippets on affected pages.
Failing code: Click Show more for the full code snippet and the option to copy to clipboard.
Effect on score: The percentage of improvement you can expect on your overall PDF compliance score if you repair the issue.
Action: Click View affected checks for the following detailed information about the failing code:
Affected checks
This view provides more detailed information about the checks that are failing for this code.
Use the tabs above the table to view the following:
Automated checks: These are accessibility checks that the scan is able to accurately identify as failing.
Assisted checks: These are accessibility checks that cannot be determined by the scan and need a human review.
Affected checks table
The table has the following columns:
Affected checks for code: The full code snippet with the option to copy to clipboard.
Effect on score: The field provides the following insights: Resolving this code will reduce the gap between your current score and 100% compliance by percentage.
Affected pages: The number of pages where this code is present across the domain.
Failing checks: The number of failing checks for this code.
Table actions
You can take the following actions on the table:
Search
Filter
Edit columns
Export
The chart displays the following information:
Check: The name of the failing check. Click the link to view all instances of this failing issue.
Pages impacted: The number of pages that contain this failing check.
Level: The WCAG criteria level.
Role: The typical role within an organization whose members have the competencies needed to resolve the issue.
Severity: The severity of the issue, Low, Medium, or High.
Actions: Expand the kebab menu and select an available action:
Open an example: Select this option to open one instance of the failing check in the Acquia Web Governance Browser Extension and view the issue on the page.
View help article: Open the Accessibility Guide article about the failing check. For more information, visit About the Accessibility Guide.
Ignore all matching code with this issue: Select this option if the issue does not need to be fixed or cannot be fixed. Ignored snippets are not taken into consideration by subsequent scans, use it only if you are certain.
Mark all matching code with this issue as fixed: After you review the issue in all of the places within the HTML code where it occurs, use this option to mark them as reviewed in bulk. For more information, visit How to review an accessibility issue.
These steps explain the process in the new navigation. If you are not subscribed to the Web Governance Early Access program, these steps may differ from your view. Contact support to join the Early Access program. All customers will automatically receive the update after the general rollout.
Introduction
The Fast track option on the left menu in Acquia Web Governance Accessibility displays accessibility issues according to the code snippets on the pages where they occur.
Fast track locates elements such as links, images, and text and addresses any accessibility and data privacy issues that are found. You can repair issues in bulk and fix, review, and ignore HTML snippets on affected pages.
Failing code: Click Show more for the full code snippet and the option to copy to clipboard.
Effect on score: The percentage of improvement you can expect on your overall PDF compliance score if you repair the issue.
Action: Click View affected checks for the following detailed information about the failing code:
Affected checks
This view provides more detailed information about the checks that are failing for this code.
Use the tabs above the table to view the following:
Automated checks: These are accessibility checks that the scan is able to accurately identify as failing.
Assisted checks: These are accessibility checks that cannot be determined by the scan and need a human review.
Affected checks table
The table has the following columns:
Affected checks for code: The full code snippet with the option to copy to clipboard.
Effect on score: The field provides the following insights: Resolving this code will reduce the gap between your current score and 100% compliance by percentage.
Affected pages: The number of pages where this code is present across the domain.
Failing checks: The number of failing checks for this code.
Table actions
You can take the following actions on the table:
Search
Filter
Edit columns
Export
The chart displays the following information:
Check: The name of the failing check. Click the link to view all instances of this failing issue.
Pages impacted: The number of pages that contain this failing check.
Level: The WCAG criteria level.
Role: The typical role within an organization whose members have the competencies needed to resolve the issue.
Severity: The severity of the issue, Low, Medium, or High.
Actions: Expand the kebab menu and select an available action:
Open an example: Select this option to open one instance of the failing check in the Acquia Web Governance Browser Extension and view the issue on the page.
View help article: Open the Accessibility Guide article about the failing check. For more information, visit About the Accessibility Guide.
Ignore all matching code with this issue: Select this option if the issue does not need to be fixed or cannot be fixed. Ignored snippets are not taken into consideration by subsequent scans, use it only if you are certain.
Mark all matching code with this issue as fixed: After you review the issue in all of the places within the HTML code where it occurs, use this option to mark them as reviewed in bulk. For more information, visit How to review an accessibility issue.