Instructions for Admin users on how to set up and configure the Accessibility feature.
Click Admin Settings (gear icon) on the top menu bar. The Domain Settings page opens.
Click Action on the same row as the domain to scan.
Select Edit Domain from the drop-down list.
The Edit Domain page opens.
When you exclude certain types of checks, you might not see other potential accessibility violations on your website.
The results show up after the next scan.
For more information, see the user guide article:
When you change the WCAG accessibility level, the existing Accessibility Score scan information is erased and the new standard starts over from the beginning with the next scan. All of the history is lost. It is advised to activate a new level only when you are ready to make the updates needed, or if it becomes a legal requirement for your location and organization.
Level AA of WCAG 2.1 is the legal requirement to be considered accessible. WCAG 2.2 is newly released and will soon be the standard, taking over from WCAG 2.1.
For a clickable demo, see:
Clickable Demo: Accessibility Setup.
For more information, see the user guide articles:
Below is a short definition of the compliance levels. Call or write to your legal department to find out the accessibility level that is necessary for the website. This will make sure that it complies with regional requirements or areas of business.
Compliance is shown for the following:
Page compliance = percentage of checks that the page is compliant in.
Domain compliance = Average page compliance in this domain.
| WCAG 2.0 (Level A): This is the minimum level of conformance. The web page satisfies all of the Level A Success Criteria, or a conforming alternate version is provided. | WCAG 2.1 (Level A): The same as WCAG 2.0 Level A, with more explanations and support material. | WCAG 2.2 (Level A): The lowest level of conformance and the easiest to achieve. It allows for websites to be broadly accessible as it addresses the most basic access issues. |
WCAG 2.0 (Level AA): The Web page satisfies all of the Level A and Level AA Success Criteria, or a Level AA conforming alternate version is provided. This check also encompasses Section 508. | WCAG 2.1 (Level AA): The same as WCAG 2.0 Level AA, with more explanations and support material. | WCAG 2.2 (Level AA): The most often used standard for legislation such as the Accessibility for Ontarians Act (AODA) and Section 508. |
| WCAG 2.0 (Level AAA): The Web page satisfies all of the Level A, Level AA, and Level AAA Success Criteria, or a Level AAA conforming alternate version is provided. | WCAG 2.1 (Level AAA): The same as WCAG 2.0 Level AAA, with more explanations and support material. | WCAG 2.2 (Level AAA): The highest level of conformance and the most difficult to achieve. It is not often used as a recommendation since it is not feasible for most websites to have the resources to meet this level. |
Info: To know more about WCAG, these sites have more information:
|
To edit the accessibility level for PDF document scans, click the new accessibility level. The default setting is WCAG 2.0.
When you change the accessibility level, the existing Accessibility Score scan information is erased and the new standard starts over from the beginning with the next scan. All of the history is lost. It is advised to activate a new level only when you are ready to make the updates needed, or if it becomes a legal requirement for your location and organization.
If you change the scan to Exclude checks that require manual review, you might not see other potential accessibility violations on your website.
How to set the accessibility level for PDF document scans:
Click to select the necessary accessibility level for PDF scans. The default setting is WCAG 2.0:
For more information, see the user guide article:
If any PDF files require remediation, this can be requested from within the Acquia Optimize platform. The remediated documents and accessibility reports are sent to you when they are ready. To include the PDF scanning tool, upgrade your account with Acquia Optimize Support.
EU customers have to contact our partner Commonlook directly for PDF remediation quotes at their own discretion due to regulatory requirements. The PDF Remediation option continues to be available for customers in other geographical regions.
Select Start PDF Accessibility Scan from the expanded menu.
On the same row as a non-compliant PDF, click to select Remediation Quote. This submits an order for remediation of issues that require attention in the PDF. This service is provided by a third party.
For more information on the PDF accessibility scan service, see the user guide articles:
This section gives instructions for admin users on how to add a custom Accessibility Statement to your website.
Click Settings (the gear icon) at the top of the Domain Overview page. The Admin Settings page opens.
Click Action on the same row as a domain to scan.
Select Script Setup Guide in the drop-down list.
Click Add PageAssist script to turn it ON.
Click the link to Open PageAssist script settings. The PageAssist script settings pane opens.
Note: PageAssist™ should be active. If the switch is not visible, refer to the user guide for instructions.
Fill in the information that the prompt requires.
For more information, see the user guide article:
PageAssist.
Tip! Use our Accessibility Statement Generator.
This section of the Accessibility dashboard shows the percentage of the site that is compliant with the accessibility level set up for your website, as well as the industry-wide average compliance score.
This figure shows the percentage of the website that is compliant with the target compliance level, as selected during scan setup. For more information, see the Accessibility Compliance Score section in this article.
This figure shows the industry-wide average of accessibility compliance. The results appear in the Accessibility Diagnostics section.
The Industry Average score is in the Accessibility Diagnostics section.
For more information, see the user guide article:
Industry Average.
This section gives information on how to navigate and edit website accessibility content.
Click Accessibility (icon of a human with arms outstretched) on the dashboard toolbar. The Accessibility dashboard opens.
The Accessibility landing page shows the selected level of compliance and the WCAG compliance for all of the lower levels. In the example above, WCAG 2.1 AA compliance is selected. The scan results show the WCAG 2.1 AA and WCAG 2.1 A compliance results.
Select this option from the menu on the left-hand side of the page. This page gives an overview of the Accessibility scan results:
Click Showing All on the top right of the section to filter for:
Industry Average: This graph gives information about how your website compliance score compares with the average of competitors in your industry.
For more information, see the user guide article:
Show History: Click this button to see the results from all scans. This information is given below in a separate section. See the History section of this document for more information.
For more information, see the user guide article:
Select this option from the menu on the left side of the page. Fix, review, and ignore HTML snippets in bulk.
The Accessibility FastTrack page opens.
For more information, see the user guide article:
Select this option from the menu on the left-hand side of the page. The list shows the URLs for pages that have accessibility issues.
The Pages with Failing Checks page opens.
It is possible to filter the list or sort for labels.
Sort between:
The table column headers are:
Labels: This column shows the labels for the domain.
For more information, see the user guide article:
Priority: This column shows the level of priority that the page has. High, Medium, or Low.
For more information, see the user guide article:
Open Page Details (the page icon): On the same row as a page with failing checks, click to open the page details.
The Page Details page opens. This page shows accessibility checks with issues and the percentage of compliance for the webpage.
Mark as fixed: Use this option when the issue is fixed on the website. Items that are marked as fixed are included in future scans.
The difference between Mark as Fixed and Ignore Check is that issues that you mark as Fixed are still included in future scans and can be flagged again if the error comes back. Issues that you mark as Ignore are permanently removed from future scans and all compliance scores.
Open Issue Page: (an i for information icon) on the same row as an issue.
For more information about Issue View see the user guide article:
Redirect to Page (magnifying glass icon): Click to navigate to the page URL and view the page as an external visitor.
Tip: If it is installed, use our web browser extension to find the errors on the page, repair the errors, and more.
For more information, see the user guide article:
Select this option from the menu on the left side of the page. This page shows a list of all checks that are done for the selected category.
Select the compliance level to filter for on the Accessibility Checklist page:
Filter the list for:
The results are shown in a table with the following headers:
Help Center: Click to navigate to the Help Center to see the details about the issue and some suggestions on how to fix it.
For more information, see the user guide article:
For a list of all of the checks, see the user guide article:
Select this option from the menu on the left side of the page. This page is a list of the most basic WCAG guidelines. The scan finds issues that do not meet the requirements.
The results are shown on this page in a table with the following headers:
Labels: This column shows the labels for the domain.
For more information, see the user guide article:
Priority: This column shows the level of priority that the page has. Priority is High, Medium, or Low.
For more information, see the user guide article:
Redirect to Page (magnifying glass icon): Click to navigate to the page URL and view the page as an external visitor.
For more information, see the user guide article:
Select this option from the menu on the left side of the page. This page shows a list of the pages that contain ignored checks.
The column headers are:
Click a page link to navigate to the WCAG Accessibility Compliance detail view for the page.
The list headers are:
Mark check as fixed: Click to mark the check as fixed. A dialog opens. Click OK to mark the check as Fixed.
The difference between Mark as Fixed and Ignore is that issues marked as Fixed are still included in future scans and can be flagged again if the error persists. Issues that are set to Ignore are permanently omitted from future scans and compliance scores.
Labels: This column shows the labels for the domain.
For more information, see the user guide article:
Priority: This column shows the level of priority that the page has. High, Medium, or Low.
For more information, see the user guide article:
Each row has the additional options to:
Redirect to Page (magnifying glass icon): Click to navigate to the page URL and view the page as an external visitor.
Tip: If it is installed, use the web browser extension to identify the placement of the errors on the page, repair the errors, and more.
For more information, see the user guide article:
Select this option from the menu on the left side of the page.
The menu expands with the following choices:
Internal PDFs: Click to select this option.
The Internal PDF Compliance page opens. This page shows the Internal PDF file accessibility compliance issues in a graph and a table.
Sort the table for issues that are:
The table menu items are:
Start PDF Accessibility Scan:
For more information, see the user guide article:
External PDFs: Click to select this option.
The External PDF Compliance page opens. This page shows the external PDF file accessibility compliance issues in a graph and a table.
Sort the table for issues that are:
The table menu items are:
For more information, see the user guide articles:
Select this option from the menu on the left side of the page.
Click to select Color Contrast Tool.
Enter the color codes of the text and background that is used on your site to see if it meets the criteria for color contrast accessibility standards.
See the contrast ratio for foreground and background color, font size, and graphical elements. The page shows how well the PDF page meets GDPR standards.
The tool gives a green PASS indicator if the color contrast is sufficient, or a FAIL indicator to let you know that the colors do not contrast enough to meet the criteria of the check.
Tip! The Color Contrast Checker web version is another quick way to test the color combinations on websites and pages, without logging in to the platform.
For more information, see the user guide article:
Quick Guide: Check and Repair Color Contrast.
Click a page link and filter for the Ignored Checks detail view for the page.
Click to select an issue. The pane on the right-hand side of the page shows actions that you can do to the issue.
Click Unignore to remove the item from the list.
This section gives instructions on how to remove a reviewed issue. Do these steps in the Audit Log section.
This procedure is for issues marked as Reviewed in the Accessibility FastTrack® module or via the Page Details view. The Undo a Check Review option returns the issue to the errors view on the page and module where it occurs.
Click Audit Log from the menu on the left side of the page.
On the same row as a reviewed issue, click Action.
The issue is gone from the audit log and returns to the errors view on the page and module where it occurs.
For more information, see the user guide article:
The orange annotation appears on the compliance chart in the Accessibility module and the Accessibility section of the History Center.
For more information, see the user guide article:
This section gives information on how to locate errors with the web browser extension.
Click Content Issues (the insect icon).
The Content Issues pane opens.
In the Accessibility section, in the same column as a failing check, click See Issues. The details pane slides open. Issues have an icon to indicate the type of issue.
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)
These issues need to be reviewed manually.
Reviews (eye icon)
These issues cannot be tested by the software and therefore need to be reviewed manually.
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. If it is not possible to repair the issue in the code, mark the issue as “Review” instead.
For more information, see the user guide articles:
The Accessibility Help Center provides guidelines on WCAG 2.0 and some common 2.1 requirements.
To navigate to the Accessibility Help Center and view all of the available articles, visit:
To access the Accessibility Help Center from within the platform interface and be directed to the specific article that is relevant to an error:
On the same row as an error, from the Check List page, the Page View, or the Accessibility FastTrack page, click Help Center (graduation cap icon).
Checklist view
Accessibility FastTrack view
For more information, see the user guide article:
The History Center stores all accessibility issues and details from previous scans.
Click History Center (bar graph icon), located on the top menu bar of any page within the platform.
The History Center landing page opens.
The page contains the following layout:
Domain: In the first field, click to expand the list of domains.
Module: In the second field, click to expand the list of available modules.
Viewing as Profile: This shows the profile that is being used.
For more information, see the user guide article:
Check frequency: The frequency of the check.
Important: The Dashboard always shows data with the default profile selected. To change this, select a new profile (click the drop-down arrow to see the available profiles). Please be aware that changing the profile causes the numbers on all 3 sections inside the Performance module to update accordingly.
The compliance score for the accessibility checks is calculated by using 100 (a perfect score) minus the number of errors found. This is then divided by the total number of accessibility checks.
For example:
If the compliance for individual accessibility checks is calculated by the
total number of pages minus pages with issues
for the
check total number of pages multiplied by 100
It will make no difference if there are 10 or 10.000 issues, it calculates the number of pages that fail the check as opposed to the total number of pages.
This section gives information about the different accessibility reports that are available.
The available reports for the Accessibility feature are:
For more information, see the user guide article:
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Wed Oct 23 2024 15:04:18 GMT+0000 (Coordinated Universal Time)