Making Your HubSpot Website WCAG 2.1 Compliant

2.4.2 Page Titled

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

Success Criteria

2.4.2 Page Titled

  • Resolved
  • Partially Resolved
  • Manually Managed
  • N/A - Level AAA
Principle: Operable
User interface components and navigation must be operable.
Guideline: Navigable
Provide ways to help users navigate, find content, and determine where they are.

Web pages have titles that describe topic or purpose.

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.4.2 Page Titled

Titles for web pages must be descriptive. Descriptive titles help users navigate through the site and find what they are looking for. In general, titles should make sense when read out of context.

Examples and Tips 

You'll want to have a consistent naming convention across your page titles. How exactly you organize the information, what separators you use, etc. are totally up to you. Just make sure your titles as clear, descriptive, and brief as possible.

  • A page title with the most important information first. The title of the page first identifies the topic of the page, then is followed by the name of the parent organization or company.

    <title> How to Write a Strong Introduction: Morey Creative Studios</title>

  • A page title divided into several parts. A web page provides guidelines and suggestions for creating closed captions. This example uses the organization, then the section of the site that the web page belongs, then the web page title itself. Similar to Example 1, both are compliant.

    <title>Morey Creative Studios | Blog | How to Write a Strong Introduction</title>

How AudioEye Helps

HubSpot and virtually all other content management systems will require the title to be in place before a page can even be published.

Notably, in addition to the many important accessibility considerations, page titles can have a material impact on SEO and AudioEye typically refrains from editing page titles. If page titles are missing or fail to be unique, AudioEye will alert Managed customers when 2.4.2 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 2.4.2 Page Titled

Download the WCAG 2.1 Compliance Checklist

Checklist Download


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

Recent Morey Creative Studios Blog Articles