Making Your HubSpot Website WCAG 2.1 Compliant

1.4.5 Images of Text

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

1.4.5 Images of Text

  • 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: Distinguishable
Make it easier for users to see and hear content including separating foreground from background.

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following:

  • Customizable: The image of text can be visually customized to the user's requirements;
  • Essential: A particular presentation of text is essential to the information being conveyed.

Note 1: Logotypes (text that is part of a logo or brand name) are considered essential.

View Official WCAG 2.1 Compliance Techniques

  • This criteria is completely resolved with accessiBe or HubSpot.


Any information that is valuable to the user should not be strictly an image. If the user might find the information useful, it should be able to be customized to fit their needs.

How accessiBe Helps

AccessiBe uses IRIS and OCR (Optical Character Recognition) to provide alt tags. Please note that accessiBe will only provide an alt tag to an image if there is no alt tag in place. AccessiBe will not replace existing alt tags.

Graphs, screenshots, and diagrams that convey information that is more than just text must include a written description of the data or include data in charts as HTML tables.


  • Logotypes
  • Small portions of an image that are not important to a user (name tags, street signs, etc. )
  • Decorative images strictly for aesthetic purposes. 


How to Test

Coming soon. 

For more information, please visit the official W3C article: Understanding 1.4.5 Images of Text

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