No shop system and no CMS makes a website accessible, and none makes it inaccessible either. The platform decides how much work the default does for you; your theme, your extensions and your content decide what your customers actually get. That is why these guides are written per system: the defaults, the extension mechanism and the typical failures differ, while the law and the benchmark – the BFSG, EN 301 549 and WCAG 2.2 AA – are the same for all of them.
Each guide answers the same questions in the same order: does the BFSG apply to a shop or site on this system, what the platform gives you and what it does not, what we find on sites built with it, which WCAG criteria to check first, a sensible order of work, and what an automated check covers and what you still test by hand.
Shop systems and CMS
-
WooCommerce
Block checkout and accessibility-ready themes are a start. Consent banners, swatch plugins, AJAX filters and payment iframes are where WooCommerce shops fail.
-
JTL-Shop
JTL calls NOVA accessible from 5.5.0. Child templates written before the update, plugins and empty img_alt fields in JTL-Wawi are where JTL shops still fail.
-
Magento / Adobe Commerce
On Magento the frontend decides: Luma-based themes carry defects Adobe itself has documented, and extensions, checkout and headless builds add their own.
-
Gambio
Gambio has fixed a lot in Malibu since 2025, but only for shops that update. Old themes, StyleEdit colours, hover-only buttons and the checkout are where Gambio shops fail.
-
Contao
Contao's core takes accessibility seriously, but many sites run on templates overridden years ago. Old templates, mobile menus, editor content and Isotope checkouts are where Contao sites fail.
-
plentymarkets / PlentyONE
Two storefronts, one ERP: theme plugins, container plugins and item data synced for marketplaces are where plentymarkets shops fail, whichever shop you run.
-
Wix
Wix writes the markup; you choose order, headings, colours, apps and alt text. Freely placed elements and App Market apps are where Wix sites fail.
-
Drupal
Drupal core has an accessibility gate. Custom themes, contributed modules and what editors put into CKEditor 5 do not – that is where Drupal sites fail.
-
OXID eShop
OXID says APEX meets WCAG level AA. Child themes frozen on old templates, modules writing into theme blocks and the checkout are where OXID shops still fail.
-
Webflow
Webflow's tested elements and Audit panel are a start. Interactions without a reduced-motion condition and widgets built from div blocks are where Webflow sites fail.
-
Joomla
Cassiopeia was built for accessibility and jooa11y checks articles. Commercial templates, old overrides and extensions with no accessibility information are where Joomla sites fail.
-
Jimdo
First check whether the BFSG applies at all. If it does: Jimdo colour sets that fail contrast, three heading sizes used for looks and pasted-in widgets are where Jimdo sites fail.
-
Squarespace
Squarespace ships a skip link, focus outlines and labelled checkout fields. Free Fluid Engine layouts, colour choices and pasted-in code are where sites fail.
-
IONOS MyWebsite
MyWebsite Now gives you heading levels, alt text and embed title fields – filling them in is your job. Unchecked AI-generated pages, weak palettes and untitled embeds are where sites fail.
-
Neos
Neos ships no front end: your agency's NodeTypes and Fusion components decide the markup. Components, alt text per image element, language fallbacks and forms are where Neos sites fail.
Earlier platform guides
- Shopware accessibility and the BFSG
- Shopify accessibility and the BFSG
- TYPO3 accessibility and the BFSG
- WordPress accessibility and the BFSG
What every platform has in common
Across systems, the same five places account for most findings: the consent banner, which sits in front of every page; product variants and filters that update without telling anyone; menus that open only on hover; sliders and galleries; and a checkout or contact form with embedded third-party fields. A platform update rarely touches any of them, because they come from the theme, from extensions or from your own content.
Whether the BFSG applies depends on what you offer, not on the software: selling to consumers online is an e-commerce service under the law, a pure information site of a private company generally is not. The overview is in BFSG for online shops and the BFSG and EAA guide.
Written to be useful, not as legal advice. As of 27 September 2026.