Why is my header/footer not optimized for accessibility?

Some older versions of the POWER theme (pre-V44) may be missing a core item to optimize them for accessibility.

1. Your base.html file may be missing a critical variable

Some older versions of the POWER theme (pre-V44)  may be missing a newer variable within their base.html file. 

In order to update this, you should access your child theme and update your base.html file. 

To access your base.html file, navigate to:  

Content > Design Manager > YOUR CHILD THEME NAME > Templates > Layouts > Base.html. 

Once in here, simply add this piece of code to the top of your file (after the greyed-out comment section) to define this new variable within your template and allow for the updated accessibility variables to be available within your theme. 

Screenshot of HubSpot's Design Manager showing the location of the base.html file in POWER THEME > templates > layouts > base.html and where to add the line of code - at the very top of the file, right after the initial comment ending with -->

Code to add:

{%- set pwr_global = {} -%}

Once this has been added in be sure to hit the orange "Publish/Update" button on the top right of your editor. 

If you have not hit the limits outlined below, this will update your header/footer to be accessibility optimized. 

2. You have too many unique menus on your page. 

Due to HubSpot limitations, HubSpot themes are limited to having  10 unique Navigation Menus on a single page. Navigation menus are configured globally via Settings > Content > Navigation Menus and can be reused across the site. 

If your page contains more than 10 unique Navigation Menus—including mega menus, modules with menu sections (like bento modules), and footer menus—HubSpot's limitations prevent the theme from utilizing its accessibility-optimized menu structure. To enhance accessibility on your website, consider reducing the number of global Navigation Menu items. You can replace them with Simple Menus, which can be configured directly within the modules, rather than relying solely on global settings.

Screenshot of the module setting Content Type - that is available for advanced content in the header mega menu, advanced footer or bento grid - showing that one can switch this configuration from "Menu" to "Simple Menu"