Making Your HubSpot Website WCAG 2.1 Compliant
The following directions are part of a full step-by-step guide to making a HubSpot website WCAG 2.1 AA compliant. These recommendations are intended for websites managed on the HubSpot CMS but can be adapted for other content management systems. In addition to explaining the WCAG Success Criteria and how to address them, this guide also describes how the AudioEye Managed solution may address each issue.
Understanding 2.4.5 Multiple Ways
The Multiple Ways criteria states that you must be able to access a webpage from all other site-pages in more than one way. For example, a main navigation alone is not acceptable.
This criteria allows users to access information more quickly and efficiently if browsing the site through a screen reader or magnifier.
If your webpage is, "the result of, or a step in, a process," this rule does not apply. An example of this would be a thank you page, like the below. Because this page occurs as a result of submitting a form, it does not need to be widely accessibly by navigation or sitemap.
Another practical example would be the WCAG Recommendations navigation on the right sidebar of this site page. The WCAG articles are accessible through this menu, the search menu and the top-level WCAG page, so this passes the criteria.
How AudioEye Helps
Within the AudioEye Accessibility Toolbar, users may engage an Accessible Site Menu, which presents a normalized visual layout that is keyboard friendly and encompasses the links made available from the various menus included within the page (emulating a site map). The menu format follows the Adobe Accessible Menu framework.
Accessible menus are also presented as they are naturally encountered by keyboard and screen reader users as they peruse the DOM. For example, as a user begins to tab their way through the site header, prior to encountering the first main navigation item, an option is presented to the keyboard user alerting them to the availability of the Accessible Site Menu.
Recommended Solutions
On the manual intervention side, the inclusion of a footer navigation, sitemap, or search function all meet the Multiple Ways standard.
For more information, please visit the official W3C article: Understanding
