HubSpot CMS EN 301 549 Checker

EN 301 549 for HubSpot CMS Sites

EN 301 549 is the European standard for accessible information and communication technology. For websites, its clause 9 reuses WCAG: version 3.2.1 uses WCAG 2.1 Level AA, and version 4.1.1, published in September 2026 for the European Accessibility Act, uses WCAG 2.2 Level AA.

The European Accessibility Act has applied to e-commerce and other consumer services since June 28, 2025, wherever the business is based. This checker runs the scan with the EN 301 549 preset, which tests the WCAG 2.1 AA web requirements. Run the HubSpot CMS WCAG 2.2 checker as well to cover version 4.1.1.

On HubSpot CMS sites run by EU public bodies or businesses, EN 301 549 covers the theme, plugins, PDFs and each language version. Cookie consent banners and language switchers are frequent sources of failures.

Who Should Run the HubSpot CMS EN 301 549 Checker

• HubSpot CMS businesses that sell products or services to consumers in the EU.
• Public sector bodies in the EU running a site on HubSpot CMS.
• Vendors selling software or services to EU public bodies.
• Non-EU companies with EU customers, since the EAA follows the customer.

EN 301 549 Requirements to Check on HubSpot CMS

• 1.4.10 Reflow

  Pages must reflow on a narrow screen without scrolling in two directions.

• 1.4.11 Non-text Contrast

  Controls, icons and focus indicators need 3:1 contrast.

• 3.1.1 Language of Page

  Each page must declare its language, which matters on multilingual EU sites.

• 3.3.2 Labels or Instructions

  Form fields, including checkout and consent forms, need visible labels or instructions.

• 4.1.2 Name, Role, Value

  Custom controls such as cookie consent switches need a name, role and state.

• 4.1.3 Status Messages

  Status messages, such as cart updates and form errors, must be announced.

Where HubSpot CMS Sites Usually Fail EN 301 549

These problems come up again and again on HubSpot CMS sites, and each one fails EN 301 549. The HubSpot CMS accessibility checker explains how to fix them in HubSpot CMS.

• Forms with placeholder-only fields. HubSpot forms output labels by default, but many are hidden or restyled so the placeholder is the only guide, which disappears when someone starts typing.
• CTA buttons and image CTAs. Image-based call-to-action buttons without alt text, and several "Learn more" buttons on one page, give screen reader users no way to tell them apart.
• Pop-ups and slide-in forms. Pop-up forms, banners and the cookie notice can open without moving focus into them, and can cover content when a keyboard user tabs to it.
• Chat and meetings embeds. The chat bubble and embedded meeting scheduler load as widgets and iframes outside your theme, with their own focus and naming problems.
• Module and landing page content. Heavy use of modules in flexible columns leads to skipped heading levels, repeated link text and decorative images read aloud as content.

Worried about ADA claims as well? The HubSpot CMS ADA compliance checker covers the HubSpot CMS risks behind most complaints.

What to Test by Hand on HubSpot CMS

Automated testing finds many, but not all, EN 301 549 failures. Check these yourself after the scan:

1. Check every language version, including the page language setting (3.1.1).
2. Test the cookie consent banner with a keyboard and screen reader.
3. Publish accessibility information for your service, as the EAA requires.
4. Rescan after each fix. Continuous monitoring rescans up to 500 URLs per domain daily and keeps a dated record in the Compliance Vault.

Start 3-day free trial

Related Guides

• EN 301 549 CheckerThe EN 301 549 standard in full, for any website.
• WCAG 3.3.2 Labels or Instructions Explained in Plain EnglishWCAG 3.3.2 Labels or Instructions explained simply: visible labels, format hints, grouped fields and required markers, with code examples and a test routine.
• WCAG 4.1.2 Name, Role, Value Explained in Plain EnglishWCAG 4.1.2 Name, Role, Value explained simply: give every control a name, role and state with native HTML and ARIA, with code examples and how to test.
• WCAG 3.2.2 On Input Explained in Plain EnglishWCAG 3.2.2 On Input explained simply: what counts as a change of context, who it helps, how to meet it with examples and code, and how to test your forms.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

HubSpot CMS EN 301 549 Checker: Frequently Asked Questions