PricingGuidesLog in
← All guides

HubSpot CMS Accessibility Checklist för Sverige

EU Accessibility Act and HubSpot CMS

From June 28, 2025, the EU Accessibility Act (EAA) requires B2B websites to meet WCAG 2.1 Level AA standards. HubSpot CMS sites built without accessibility in mind create barriers for users with disabilities — and expose your organization to legal and reputational risk. This checklist covers six critical issues that appear frequently in HubSpot implementations and how to fix them.

Image Alt Text

  • [ ] Open a page in HubSpot Content Editor. Select each image module and check the Alt Text field is filled in.
  • [ ] Alt text should describe what the image shows, not just say "image" or repeat the surrounding text.
  • [ ] For logos or decorative images, you can leave alt text empty — but only if the image isn't carrying meaning.
  • [ ] How to check on HubSpot CMS: Click any image, look for the Alt Text input in the right panel. If it's blank, fill it in with a short, descriptive phrase (10–15 words is typical).

Color Contrast

  • [ ] Check that body text has a contrast ratio of at least 4.5:1 against its background (or 3:1 for large text).
  • [ ] Test your chosen color palette using a free tool like WebAIM Contrast Checker or Stark before publishing.
  • [ ] This is especially important for call-to-action buttons, form fields, and any text over image backgrounds.
  • [ ] How to check on HubSpot CMS: Use your browser's developer tools or a contrast checker browser extension while viewing your published page. Paste the button or text color hex codes into the tool. If the ratio falls below 4.5:1, adjust the color in HubSpot's module styling.

Form Field Labels

  • [ ] Every form input (text field, email, dropdown, checkbox) must have a visible label connected to it.
  • [ ] In HubSpot Forms, ensure the Label field is populated and the Hide Label toggle is OFF (unless you use a placeholder, which is not a substitute for a label).
  • [ ] For custom forms built with custom HTML modules, wrap inputs in `<label>` tags or use the `aria-label` attribute.
  • [ ] How to check on HubSpot CMS: Open your form in the editor. Click each field and confirm a label appears on the published page and is linked to the input (not just nearby text).

Link Text and Purpose

  • [ ] Every link must have readable text that tells users where it goes or what happens when clicked.
  • [ ] Avoid "click here," "read more," or "learn more" as standalone link text — use "Read our accessibility guide" or "Download the pricing guide" instead.
  • [ ] If a link contains only an icon or image, add descriptive alt text to the image or use a hidden text label.
  • [ ] How to check on HubSpot CMS: Scan your page for links. Right-click each one and inspect the text. If you see only an icon or empty anchor tag, edit the module and add clear link text or alt text.

HTML Document Language

  • [ ] Check that your HubSpot site's HTML `<html>` tag includes a `lang` attribute (e.g., `lang="sv"` for Swedish or `lang="en"` for English).
  • [ ] If your site serves both Swedish and English, each version must declare its own language.
  • [ ] How to check on HubSpot CMS: View the page source (Ctrl+U or Cmd+U). Look at the very first `<html>` tag. If it says only `<html>` with no `lang` attribute, contact your HubSpot developer or check HubSpot's Site Settings to add it. This is typically a site-wide setting, not per-page.

Button Labels

  • [ ] Every button must have visible or hidden text that describes what it does.
  • [ ] Avoid icon-only buttons. If you use an icon button, add a hidden label using `aria-label="Button text"` or wrap it in a visible label.
  • [ ] In HubSpot modules, check that button text is clear: "Request a demo," "Download whitepaper," or "Contact sales" — not just "Submit" or "Go."
  • [ ] How to check on HubSpot CMS: Click each button on your page. If it contains only an icon or no visible text, edit the module and add descriptive button text or add an `aria-label` attribute via custom code if needed.

Final Steps

Accessibility is an ongoing commitment, not a one-time checklist. Test your site with real assistive technology (screen readers like NVDA or JAWS), keyboard navigation (Tab key only), and automated tools like Axe or Lighthouse in Chrome DevTools. Train your content team to apply these practices to every new page. By June 28, 2025, regulators will expect compliance — but more importantly, accessible design makes your B2B site more usable and professional for all visitors.

This is technical WCAG guidance, not legal advice.

Related guides