For Hubspot forms that we're using, the validation errors are not being read by screen readers. When inspecting the errors, it seems that the HTML code used is not allowing the alert to be read properly. Below are the suggestions to allow the error messages to be accessible even when it's an inline messages. Removing role=alert from the error messages. Changing the error messages to be contained in an inline element like SPAN adding unique ID to the alert messages. The error messages and the fields are connected using Aria-Labelledby.
... View more
As the title states, it would be awesome to have the ability to limit what module options are available to be used for Drag and Drop, or Flexible areas on a landing page. As a developer to be able to lockdown what modules can be used by marketers when they are using that template to make pages.
Internal process documentation helps with this. However in our experience process docs don't always sufficiently help avoid the problem of people placing modules onto pages that are not built to be on. Nor do we as a Hubspot partner working on client portals often have real control over the assets(example: fun modules purchased from hubspot marketplace) that exist in a client portal.
Because of things like this, having the ability on the template level to allow, or disallow any number of custom modules or modules would be awesome! Especially in the age of Hubspot Marketplace, results in portals with tons of custom modules that often times will only properly display as intended on a specific template.
... View more