A Better Prompt Won't Fix This: The Accessibility Failures That Survive AI UI Generation

Two AI-built storefronts audited against WCAG 2.2 AA hit the same four critical failures despite very different prompts. Prompt harder isn't the fix — a review pass is.

accessiBe audited two Lovable-built storefronts on 2026-06-16 against WCAG 2.2 AA, using screen readers and keyboard testing rather than a scanner alone. One was built from a one-line prompt, the other from a detailed, iterated brief. The detailed brief did help — 9 issues versus 15. But accessiBe reports both sites shared the same four critical failures. Better prompting moved the minor problems and left the serious ones untouched.

That result makes sense once you notice what the model is optimising for. ARIA roles, focus order, and accessible names are invisible in a rendered screenshot, so a model trained toward visually plausible output has no signal pushing it to get them right.

The recurring four, worth checking in any generated UI:

1. Overlays — modals, drawers, newsletter popups — with no role="dialog", no accessible label, no focus trap, no Escape handler. Focus stays on the page behind.
2. Inputs labelled only by placeholder text, which disappears on typing and is not an accessible name.
3. Contrast failures, usually on sale badges and secondary text.
4. Information carried only visually — a struck-through price, a colour-coded state — with no text equivalent.

Where to put the effort. master.dev's write-up found ten distinct failures in a single generated sidebar, and puts prevention at 3–8 minutes per component against 45–90 minutes to remediate after launch. The cheap layers, in order: generate onto accessible primitives (Radix, React Aria — this is why v0's shadcn output starts ahead), then eslint-plugin-jsx-a11y for static checks, then jest-axe or @axe-core/playwright in CI.

The limit worth knowing: automated tooling catches roughly a third of WCAG criteria. Focus order, screen-reader narrative, and whether a flow makes sense without sight need a human keyboard pass — tab through the thing once before you ship it.

Sources: accessiBe: AI storefront accessibility audit · master.dev: AI-generated UI is inaccessible by default · W3C WAI evaluation tools