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 3.3.2 Labels or Instructions
Criteria 3.3.2 states that if there is a situation where user's input is required—like a form—there is a clear label or instruction requiring an explanation of the information required.
How HubsSpot Helps
When you create a form with HubSpot, by default it applies a descriptive label which meets both the visual and code criteria for compliance.
You have full customization over the label to change the messaging. HubSpot does not prevent you from removing the label entirely, however that is not recommended as it would negate compliance for this criteria.
How AudioEye Helps
In the event that labels are missing, AudioEye will—through automated and manual processes—apply descriptive labels and/or additional ARIA attributes.
Recommended Solutions
We recommend keeping the default HubSpot label to ensure compliance. If you do need to change the messaging, just ensure you replace it properly so that all forms have a label at all times.
If you have previously solved for 1.3.1 Info and Relationships, you should already be compliant for this criteria.
For more information, please visit the official W3C article: Understanding
