Making Your HubSpot Website WCAG 2.1 Compliant

2.1.1 Keyboard

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.1.1 Keyboard

  • Resolved
  • Partially Resolved
  • Manually Managed
  • N/A - Level AAA
Principle: Operable
User interface components and navigation must be operable.
Guideline: Keyboard Accessible
Make all functionality available from a keyboard.

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.
Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

View Official WCAG 2.1 Compliance Techniques

  • This criteria is not resolved with accessiBe or HubSpot and requires manual management.


This criteria ensures that content can be accessed with just keyboard functions and people that are blind or have low vision and people that use keyboard emulators can still access the content.

Most actions performed by a pointing device such as a mouse can be done from a keyboard like clicking and selecting text. However there are a few tasks that can't be done from a keyboard such as free hand drawing, painting, and or games that require eye hand coordination from a pointing device.

How accessiBe Helps

Unfortunately accessiBe or HubSpot do not provide any programming to allow content to be operated through a keyboard functions. However, just because this is not automatically resolved does not mean that you're not meeting the criteria's standards. The average website does not have the need for this type of keyboard functionality (e.g. free hand drawing), so most likely your website meets this standard.


As previously stated, the average website will not require this functionality, and you will be compliant by default.

However, if you do require these advanced functions, we recommend familiarizing yourself with the W3C instructions, and use these GitHub templates as a jumping off point.

For more information, please visit the official W3C article: Understanding 2.1.1 Keyboard

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