At present, HubSpot embedded forms do not meet common standards for accessibility compliance. To meet common standards such as WCAG 2.0 several changes would be required, for example:
Focus States:Clearly indicate which element has focus when navigating with a keyboard. For example, on form submit if a user has not completed a required field the focus should go to the required field and the error message should be labeled relevant to that field, not the whole form.
Required field labels: Similarly, required form fields should be labeled, (for example include aria-required="true") to inform screen-reader users of the field's validation.
Name, Role, Value: Providing role, state, and value information on all user interface components enables compatibility with assistive technology, such as screen readers, screen magnifiers, and speech recognition software, used by people with disabilities. While HubSpot forms can be labeled in the form editor, form elements should have unique IDs to ensure that their corresponding labels provide accurate information and this isn't always true, nor can labels be edited easily in the embedded form.