BFSG & WCAG 3.0 for Vendure Storefronts

Since 2025 the German Accessibility Strengthening Act (BFSG) is binding for most online shops. For teams building on Vendure, a code-first framework where the frontend is yours to own, that raises a direct question: where does accessibility actually get solved, and who owns the work?

Accessibility is a frontend problem

Compliance is judged on what users experience: keyboard navigation, focus order, semantic structure, color contrast, screen-reader labels and accessible forms. All of that lives in the rendered frontend. The Vendure Shop API serves correct data; whether the result is accessible depends entirely on the frontend layer.

What BFSG and WCAG 3.0 require in practice

• Perceivable content: sufficient contrast, text alternatives, scalable text
• Operable interfaces: full keyboard operation, visible focus, no keyboard traps
• Understandable flows: consistent navigation, clear form labels and error messages
• Robust markup: valid semantics and ARIA where needed, tested with assistive technology
• The standard also tracks EN 301 549, the European baseline referenced by the regulation

The cost of retrofitting

On Vendure's Next.js storefront or a fully custom frontend, accessibility is your responsibility, the same way the rest of the frontend is. That usually means a separate audit, a remediation backlog and recurring regression risk every time a component changes. Accessibility added late is expensive and fragile.

Laioutr delivers the baseline by default

With Laioutr, WCAG 3.0, BFSG and EN 301 549 are part of the platform baseline. The component library ships with accessible semantics, focus handling, contrast-compliant defaults and screen-reader support, so the storefront starts compliant rather than being audited into compliance later. Because components are maintained centrally, accessibility does not regress every time marketing composes a new page.

What still needs attention

Platform-level accessibility covers components and structure. Content teams still own accessible content: meaningful alt text, sensible heading order and clear link text. Laioutr makes the compliant path the default; teams stay responsible for the words and images they add.

FAQ

Does Vendure make my storefront BFSG-compliant?

Vendure serves data through the Shop API; accessibility is decided in the frontend. Compliance depends on the frontend layer rendering that data accessibly.

Do we still need an audit with Laioutr?

The platform baseline covers component and structural conformance. A content review and a confirmatory audit are still good practice, but you are not building compliance from zero. Talk to our team.

Does compliance slow down marketing?

No. The accessible path is the default in the page builder, so teams compose compliant pages without extra steps.

More on Laioutr: B2C Growth Kit.

Related reading: BFSG & WCAG 3.0 for SCAYLE Storefronts and BFSG & WCAG 3.0 for SAP Commerce Cloud Storefronts.