Notes on shipping accessibility guardrails for a low-code builder

the constraint

The end-user of a low-code builder is rarely a developer. They're a business analyst, a marketer, an ops lead. They're building forms, dashboards, internal tools — at speed.

If you make accessibility a thing they have to remember, they will not remember.

what worked

Defaults that pass WCAG. Color picker doesn't show colors with insufficient contrast against the chosen background. The 80th-percentile choice is automatically AA.

In-line warnings, not blocking errors. A small "⚠ low contrast" badge next to the offending element on the canvas. Visible. Ignorable. But once you've seen the badge ten times, you notice it.

Sensible fallbacks for skipped fields. No alt text? Generate [image] as a stub and surface a list of stubs on a single "accessibility check" panel. One panel, one place to fix.

what didn't

Hard blocks at publish. Users find a workaround. The workaround is worse.

Education tooltips. Nobody reads them on the third Tuesday at 4pm.

Lint-style messages in dev tools language. "WCAG 2.2 SC 1.4.3 fail" means nothing if you're a marketer. "Low contrast — hard to read" works.

the principle

Make the right thing the path of least resistance. Make the wrong thing visible. Don't make the wrong thing impossible — that just relocates it.