Making Your HubSpot Website WCAG 2.1 Compliant

2.1.1 Keyboard

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.

LEVELA
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 partially resolved and/or detected with AudioEye Managed but may require some manual intervention and/or collaboration with AudioEye.

Understanding 2.1.1 Keyboard

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

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 AudioEye Helps

AudioEye offers several keyboard-centric features. From the Visual Toolkit, users may enable a Keyboard Focus utility, which forces an accessible style schema to ensure elements receiving focus are properly conveyed.

Screenshot of AudioEye Visual Toolbar with keyboard focus selected

Warnings

The AudioEye Visual Toolkit can adjust the formatting of a website, but it is not intended as a replacement for making the necessary visual improvements that help ensure an optimal visual experience for individuals with disabilities. AudioEye collaborates with Managed customers to assist them in identifying and understanding keyboard accessibility issues. When designing your site, try to be mindful to test the user experience from the perspective of someone relying solely on the use of the keyboard to engage and interact with your site.

As it pertains to ensuring all features and functionality may be controlled without the use of a mouse or visual point-and-click devices, AudioEye collaborates with Managed customers to determine any necessary remediations associated with highly dynamic features. However, tThe 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.

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

Questions?

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

Recent Morey Creative Studios Blog Articles