Making Your HubSpot Website WCAG 2.1 Compliant

3.2.4 Consistent Identification

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.

LEVELAA
Success Criteria

3.2.4 Consistent Identification

  • Resolved
  • Partially Resolved
  • Manually Managed
  • N/A - Level AAA
Principle: Understandable
Information and the operation of user interface must be understandable.
Guideline: Predictable
Make Web pages appear and operate in predictable ways.

Components that have the same functionality within a set of Web pages are identified consistently.

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 3.2.4 Consistent Iden

Criteria 3.2.4 states that any items that share functionalities—icons, navigation links, etc.—are consistently named and labeled. This makes it easy for users to logically navigate and understand site structure.

An example of this criteria in practice is the guiding navigation at the bottom of this post stating, "Next Article: 3.2.5 Change on Request." Every post in this series of blogs has a similar next article link, that will consistently take you to the next article, and there will not be a circumstance where the next article function takes you to the previous post, or the homepage.

It's interesting to note that consistent does not imply identical. For example, the next article function will not always say, "Next Article: 3.2.5 Change on Request." as the posts will continue to increase, and the number variable will change.

If you are using icons, the same icon can be used differently site-wide as long as they serve separate functions and are labeled properly. For example, you can use an X icon to convey 'close' and also 'not included,' with the proper labels. however, if you were to use an X icon to convey 'close' and 'exit,' this would be a failure of the criteria as they're similar functions but inconsistent labeling.

Another note to keep in mind is that aria labels must be kept consistent across elements, or it is also considered a criteria failure.

How AudioEye Helps

AudioEye will alert Managed customers when 3.2.4 violations are detected and can take action with customer approval. However, for instances where Managed customers do have full control to remediate the source issue, AudioEye will collaborate with accessibility stakeholders to instruct them on what specific changes are required, why the changes are important, and how the changes can be implemented.

For more information, please visit the official W3C article: Understanding 3.2.4 Consistent Identification


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