Making Your HubSpot Website WCAG 2.1 Compliant

1.4.13 Content on Hover or Focus

MCS Accessibility Team

MCS Accessibility Team
Last Updated July 23, 2020

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.

Success Criteria

1.4.13 Content on Hover or Focus

  • Resolved
  • Partially Resolved
  • Manually Managed
  • N/A - Level AAA
Principle: Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
Guideline: Distinguishable
Make it easier for users to see and hear content including separating foreground from background.

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

  • Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
  • Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
  • Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

View Official WCAG 2.1 Compliance Techniques

  • This criteria is partially resolved and/or detected with AudioEye Managed but may require some manual intervention and/or collaboration with AudioEye.

Understanding 1.4.13 Content on Hover or Focus

This Success Criterion regards any web item that can only be viewed on hover. For users that have low vision, limited mobility, or use keyboards as their sole navigation tool, certain parameters need to be met so that they can successfully interact with the hovered content. To do so, this content needs to be:


The purpose of this criteria is to prevent interference of the original website's content when interacting with content that appears once a specific prompt is hovered over. When a hover-prompted item is activated, it typically blocks out other elements on the page. For a user that has a magnified viewport and uses their cursor to pan the screen, they may risk re-triggering the hover when trying to navigate around. Alternatively, there are users who do not use a mouse and instead navigate websites using their keyboard exclusively. Two methods to satisfy this criteria include:

  • Positioning the hovered content in an area that doesn't obstruct any on the screen including the hover trigger. This excludes any white space or background images.
  • Allow for the hovered item to be dismissed using a keyboard, such as the Escape button.

This criteria does not include error messages that require attention or action.


Oftentimes, when the cursor is moved away from prompt that causes the hovered element to appear, this triggers the element to disappear. For example, if there is a text prompt that says "Click Here" and upon hover of it, a text box appears with additional information. If the user moves their mouse through this box, it will leave the space where "Click Here" is stated. In many cases, this will make the box disappear. This is a problem for cases where users may need or want to use their cursor to follow the content of the hovered item. To remedy this, hovered content should remain visible until one of the following parameters are met:

  • The cursor is moved off the prompt OR any part of the hovered element.

  • The hovered item is dismissed using a method that satisfies the Dismissible criteria, such as using the Escape key on the keyboard.

  • The information in the hovered content is no longer relevant - such as a "busy" message on an item that has been completed.


In certain cases, a hovered element has a time-limit to how long it is open and if an item is hovered over for long enough, this element will disappear. Users with disabilities may require additional time to review the content. To fulfill this criteria, hovered content must remain visible until a user removes focus from the trigger/hovered item, or uses a Dismissible method such as the Escape key.

Making sure users with disabilities can engage appropriately with hovered items is an important part of their web experience and should not be overlooked.

How AudioEye Helps

AudioEye is capable of making visual adjustments to a website, but these steps are taken only as a last resort and if a digital access barrier is fully limiting access for end-users. As these actions would impact the visual display of the site, they would also require explicit written approvals to change. When 1.4.13 violations are detected, AudioEye will alert and collaborate with accessibility stakeholders to incorporate the necessary best practices in connection with the design, development, and content creation process.

For more information, please visit the official W3C article: Understanding 1.4.13 Content on Hover or Focus

Download the WCAG 2.1 Compliance Checklist

Checklist Download


Let us know if we can help you address this specific WCAG Recommendation.

Recent Morey Creative Studios Blog Articles