Vibe Design Is Cool. But Is It Accessible?

Google just overhauled its AI design tool, Stitch.

The pitch is simple. Describe what you want, or say it out loud, and Stitch generates a polished UI in seconds. Screens, flows, components, even a design system.

From a speed standpoint, it’s impressive.

But here’s the real question.

Does it produce accessible output?

There are two things that matter here, and they are not the same.

First, can disabled creators actually use Stitch?
Second, does Stitch generate UI that works for disabled users?

On the creation side, voice input is a nice addition. But I haven’t seen clear documentation around screen reader support, keyboard navigation, or how the tool behaves for blind users or anyone relying on assistive tech. That doesn’t mean it fails. It means Google hasn’t shown its work.

On the output side, the gap is more concerning.

I haven’t seen any claim that Stitch-generated designs meet WCAG 2.2, or even consistently handle basics like contrast, focus order, labeling, or touch targets.

And that’s the whole game.

Accessibility isn’t about how clean something looks. It’s about whether it actually works. Can you navigate it without sight? Can you tab through it logically? Can a screen reader make sense of it? Can someone with low vision or motor limitations use it without friction?

Right now, Stitch looks like a rapid prototyping tool, not an accessibility-first design platform. It appears to be optimized for speed, iteration, and design handoff. That has real value. But unless and until Google clearly documents WCAG-aware output rules, built-in accessibility checks, and accessible authoring support for disabled creators, nobody should assume Stitch gives you accessible UI just because it gives you pretty UI.

And that assumption is dangerous.

Because if teams start treating AI-generated interfaces as production-ready without accessibility review, blind users, low vision users, keyboard-only users, deafblind users, people with cognitive disabilities, and everyone else who depends on accessible design will once again be handed the bill for somebody else’s shortcut.

That is not innovation. That is technical debt with a prettier landing page.

The better question for Google is not whether Stitch can generate a UI in seconds.

It’s this.

Can it generate interfaces that actually work for everybody?

Right now, I don’t think Google has publicly proven that it can.

Until it does, treat Stitch as a brainstorming engine. Not an accessibility guarantee.

Mike Calvo

CEO, Pneuma Solutions