HubSpot CMS Section 508 Checker

Section 508 for HubSpot CMS Sites

Section 508 of the Rehabilitation Act requires federal agencies to make the information and communication technology they develop, buy, maintain or use accessible. The Revised 508 Standards, in effect since January 2018, incorporate WCAG 2.0 Level A and AA for web content, electronic documents and software.

Private businesses are not directly covered, but agencies must buy accessible technology, so vendors are often asked for an Accessibility Conformance Report (ACR) based on the VPAT. This checker runs the scan with the WCAG 2.0 AA preset that Section 508 uses.

HubSpot CMS is often used for agency and university sites. Under Section 508, the theme, plugins and every PDF you publish are in scope, so scan the templates and check documents with a PDF accessibility checker.

Who Should Run the HubSpot CMS Section 508 Checker

• Federal agencies running a site or microsite on HubSpot CMS.
• Contractors and vendors whose HubSpot CMS site or portal is part of a federal contract.
• Agencies and vendors preparing a VPAT or Accessibility Conformance Report.
• State bodies and universities whose policies adopt Section 508.

Section 508 Checks That Matter for HubSpot CMS Sites

• 1.1.1 Non-text Content

  Every image, icon and chart needs a text alternative, or must be marked as decorative.

• 1.3.1 Info and Relationships

  Headings, lists, tables and form labels must be marked up so assistive technology can read the structure.

• 1.4.3 Contrast (Minimum)

  Text needs a contrast ratio of at least 4.5:1, or 3:1 for large text.

• 2.1.1 Keyboard

  Every function must work with a keyboard alone.

• 2.4.1 Bypass Blocks

  Provide a way to skip repeated navigation, such as a skip link.

• 4.1.2 Name, Role, Value

  Custom controls need a name, role and state that assistive technology can read.

Where HubSpot CMS Sites Usually Fail Section 508

These problems come up again and again on HubSpot CMS sites, and each one fails Section 508. 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, Section 508 failures. Check these yourself after the scan:

1. Test every page with a keyboard only, including menus and dialogs (2.1.1).
2. Check documents and PDFs separately, since Section 508 covers them too.
3. Record results per criterion if you need to complete a VPAT or ACR.
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

• Section 508 CheckerThe Section 508 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 Section 508 Checker: Frequently Asked Questions