Making Your HubSpot Website WCAG 2.1 Compliant

2.5.2 Pointer Cancellation

MCS Accessibility Team

MCS Accessibility Team
Last Updated November 09, 2019

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. All suggestions in this guide are in conjunction with the accessiBe solution and require an active license. For more information on the accessiBe platform and pricing, you can learn more here.

Success Criteria

2.5.2 Pointer Cancellation

  • Resolved
  • Partially Resolved
  • Manually Managed
  • N/A - Level AAA
Principle: Operable
User interface components and navigation must be operable.
Guideline: Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential.

View Official WCAG 2.1 Compliance Techniques

This criteria applies specifically to non-standard on-click events. If you're just using standard HTML components, you'll resolve this criteria and be compliant by default. No manual intervention will be required, and you can stop reading right here!


This success criteria helps anyone with mobility or cognitive disabilities who may click or touch the wrong spot by mistake. This criteria will ensure that people will not experience something that is unexpected. This criteria mainly relates to interactive elements.

No Down-Event

When you press a mouse button down, touch down on a surface, or down on a key; this is considered a down event. 

Abort or Undo

The user can verify that the pointer is over the location before releasing and completing the action. The undo would take place if the user drags the pointer anywhere but the desired location. Basically if you hover your pointer over a location it does not complete the event until the up event. An undo button can be implemented as well. 

Up Reversal

This is similar to "Abort and Undo." To cancel an unintentional action a user can drag the pointer off the desired location and release. If hovering over the wrong locations, the user can simply drag off of the location to undo it. 


Anything that would require an action on the down event and otherwise would be unnatural. Such as pressing on a horn in a car simulator. The action would be odd if the action happened upon release and not on the down event. 

An example of this is a simple link!
Click Here!

If you click down on the link above and move the cursor off of the link, the action will be canceled. The link will only activate on the up event. 

Best Practices

Only use the down-event when it is necessary. Design actions to take place on the up event and implement a function to abort/undo. 

How accessiBe Helps

accessiBe will not rewrite javascript on the fly. 

For more information, please visit the official W3C article: Understanding 2.5.2 Pointer Cancellation

Download the WCAG 2.1 Compliance Checklist

What to expect if you download this checklist

Video: What to Expect If You Download this Checklist

Checklist Download


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

Recent Morey Creative Studios Blog Articles