Making Your HubSpot Website WCAG 2.1 Compliant

1.3.2 Meaningful Sequence

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.

LEVELA
Success Criteria

1.3.2 Meaningful Sequence

  • 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: Adaptable
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

View Official WCAG 2.1 Compliance Techniques

  • This criteria is not resolved with accessiBe or HubSpot and requires manual management.
"This criteria aims to ensure that the order of the info and content on your web page is clear for all users."


Understanding

If the content on your page is not in a "meaningful sequence", screen readers and other assistive technology will read the content in the wrong order, creating confusion and disorientation from users. 

This criteria also comes into play when using white space characters (space, tab, line break) instead of appropriate HTML elements. See examples below.

*This criteria only applies when the order of your content affects the meaning of your content.

Examples and Tips

This criteria can mostly be satisfied by thoughtful programming, that is, keeping in mind the order of your content as you develop it. However, there are some failures that can occur outside of the norm.

Common failures for this criteria include:

  • Using white space characters to format HTML tables, instead of using headers.
  • Using tab to format lists instead of the appropriate list HTML element. 
  • Using white space characters to control letter spacing instead of the letter-spacing CSS property

 

Our biggest tip for checking this criteria on your page is to remove styling from your page and read through your content to ensure it is laid out in a meaningful way. Then add your styling to the page and make sure the sequence is maintained. 

If, as a developer or designer, you need to order your content in a way that does not match this criteria, there are attributes and techniques you can utilize. 

How accessiBe Helps

This criteria is only violated when a developer/designer structures the content in a non-meaningful way. Because of this truth, accessiBe is unable to account for the mind of the designer/developer, which means this is a manually resolved criteria.

For more information, please visit the official W3C article: Understanding 1.3.2 Meaningful Sequence


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