EAA compliance for Bubble: WCAG 2.1 AA checklist & fixes

What the EAA actually requires from a Bubble site

Bubble is a no-code platform that renders generic div-based markup with limited accessibility primitives, so under the EAA the obligation is unusually demanding because the platform does not nudge you toward semantic HTML. EN 301 549 conformance forces you to manually set programmatic labels on inputs that default to placeholder-as-label, give list semantics to repeating groups that render as plain divs, and audit any raw-HTML embed where none of Bubble's accessibility helpers run. The requirement effectively means sweeping every interactive element's Accessibility tab, because nothing is accessible by default.

Bubble is used by non-technical founders building B2B SaaS and internal tools, so many in-scope apps are B2B services in the EAA's later-transition scope, with consumer-facing Bubble apps in immediate scope. These are typically small startups facing fixed national fines rather than turnover-percentage penalties, but the deeper risk is architectural: because the platform fights semantic HTML, reaching AA on Bubble is expensive and may raise a strategic question of whether a consumer-facing product should stay on Bubble at all. The fine is often less costly than the ongoing accessibility tax.

Remediation is done by the app builder inside Bubble's editor, using the per-element Accessibility tab (off by default) to set ARIA labels, roles, and logical tab order on every interactive element, plus custom HTML elements for skip links and landmarks. Because Bubble offers no code layer to fix things globally, this is a manual element-by-element sweep before launch, and it must be verified against the live URL rather than the editor preview. Expect materially more accessibility effort than a coded equivalent of the same app.

Top WCAG failures we see on Bubble sites

Across hundreds of Bubble scans, the same handful of issues show up over and over. None of them require ripping the theme apart — most are fixable in a few hours by someone comfortable in the platform's editor or template files.

• Inputs without programmatic labels by default

  Bubble form inputs ship with placeholder-as-label patterns.

  3.3.2, 1.3.1 — Level A

• Repeating groups rendering as <div>s without list semantics

  Lists of items are not announced as lists by screen readers.

  1.3.1 — Level A

• Custom HTML elements bypassing Bubble accessibility checks

  When you embed raw HTML, none of Bubble's accessibility helpers run.

  all

Concrete code fixes for Bubble

Below are copy-paste fixes for the most common Bubble issues. They assume you have access to your theme code or the platform's custom-code injection panel. If you cannot edit code directly, share these snippets with whoever maintains the site — every one of them is a ten-minute change.

// Workflow: every input element → Inspector → Accessibility tab
//   - Set ARIA label
//   - Set role explicitly if not native
//   - Confirm tab order is logical

Tools and plugins worth installing first

• Bubble's built-in Accessibility tab

• Custom HTML element for skip links and landmarks

How to scan a Bubble site without missing anything

Automated scanners catch about 30–40% of WCAG issues; the rest need manual review. The good news is that the 30–40% includes the most expensive issues to remediate after the fact, so an automated scan is the cheapest way to get unstuck. Run one before you change a line of theme code.

• Scan the live URL, not the editor preview.