Introduction¶

Acquia Optimize provides a built-in accessibility guide for website accessibility issues. The accessibility guide gives details about the issues that the scan finds on your website and gives tips on how to fix them.

Access the accessibility guide¶

The Accessibility guide provides guidelines on the level of WCAG requirements. Visit Acquia Optimize accessibility guide to view all of the available articles.

To access the Accessibility guide from within the Acquia Optimize interface and navigate directly to the relevant article for an error:

1. On the same row as an error, from the Check List page or from the Accessibility FastTrack page, click Help Center (graduation cap icon).

   Checklist view

   

   Accessibility FastTrack view

   
2. The Accessibility Help Center page opens. Find information about the issues and instructions on how to fix them.

3. Click Open New Help Center for added details about the WCAG 2.2 check.

   The information about the check includes:

   • The name of the check
   • Impact
   • Difficulty
   • Guidelines
   • Tags
   • Why is this an issue
   • Examples (if available).

WCAG 2.2 Guidelines¶

To support the new guidelines from the update to WCAG 2.2, Acquia Optimize has launched a new support center for accessibility.

Access it from within the existing help center.

The new WCAG 2.2 guidelines add the following checks:

New checks, in addition to previous recommendations from the WCAG 2.1 guidelines, include:

• For steps in a process, information previously entered by or provided to the user that is required on subsequent steps is either auto-populated or available for the user to select.
• If a cognitive test (such as memorizing a username and password) is required to log in, an alternative method of authentication that does not require a cognitive test (such as permitting copy and paste function) must also be provided.
• Essential controls such as edit buttons should remain visible and/or accessible while they are relevant, rather than being hidden and/or invisible until a mouseover or focus is applied to them.
• If a help option is made available, it should be consistently accessible in the same relative location so it can be found easily.
• All interactive targets (such as linked icons) must take up a minimum of 44x44 CSS pixels of space. This can include white space surrounding the target.
• If dragging movements are needed (for example, to change a slider), an alternative method such as a mouse click or tap (on a touch-screen) should be provided.
• Make sure that all publications have page numbers and that those numbers match any corresponding version (such as zoomed in or viewed elsewhere) or the printed version, if any.
• When receiving keyboard focus, User Interface components must have a minimum focus indication area that contrasts sufficiently with both the colors of the unfocused state and with the adjacent colors. In addition:
  • The item with focus applied to it must not be obscured by author-created content.

  • When receiving keyboard focus, User Interface components must have a minimum focus indication area that contrasts sufficiently with the colors of the unfocused state.

    Tip! The Acquia Optimize Color Contrast Checkeris a quick way to test the color combinations on websites and pages. For instructions, see the Quick Guide: Check and Repair Color Contrast

Additional resources¶

For more information about accessibility requirements:

• The official site for Web Content Accessibility Guidelines
• The official site for Section 508 of the Rehabilitation Act
• Quick Reference: How to Meet WCAG 2.1 Requirements