Gambio is neither accessible nor inaccessible on its own. What counts is what your shop renders: the theme and its StyleEdit settings, the widgets on your start page, your modules and your product data. Since 2025 Gambio has shipped a run of accessibility fixes in its default theme, Malibu – but they reach a shop only through an update, and some of them only reach new shops. This page separates what Gambio gives you from what stays your job, and names the places to test first.
Does the BFSG apply to your Gambio shop?
If you sell to consumers through Gambio, you provide an e-commerce service – in the words of the law, a "Dienstleistung im elektronischen Geschäftsverkehr" (§ 1(3) no. 5 BFSG). In Germany the Barrierefreiheitsstärkungsgesetz has applied to such services since 28 June 2025. It transposes the European Accessibility Act, so shops selling into other EU countries meet equivalent national laws there [1][2].
Gambio is built for merchants who run a shop without a developer [3], so check the exemption first. Micro-enterprises that provide services are exempt: fewer than 10 employees and an annual turnover or balance sheet total of no more than €2 million (§ 2 no. 17, § 3(3) BFSG) [1]. Both conditions must be met. How to count staff, and what applies if you also sell through marketplaces, is explained on our page on the micro-enterprise exemption. A purely B2B shop that only sells to business customers is not a service to consumers; if you sell to both, treat the consumer side as covered.
Scope, market surveillance and the information you have to publish are explained in BFSG for online shops. If you are weighing Gambio against another system, the same questions for JTL-Shop, Shopware and WooCommerce are answered on their own pages.
What the platform gives you, and what it does not
You get:
- A default theme with documented fixes. Service Pack 4.9.5.0 brought "improvements for accessibility" and alt attributes for the images of Malibu's default start page, explicitly "for BFSG" [4]. 4.9.6.0 added missing
<legend>elements to the registration, price filter, contact and login forms and better ARIA roles in the product filter [5]. 5.0.0.0 named the quantity controls and made the password checkbox work with the space bar [6]. - A vendor statement you can hold the theme to. When 4.9.5.0 came out, Gambio wrote in its forum that in new shops Malibu and Honeygrid are completely prepared for accessibility as shipped [9]. A useful baseline, not evidence about your shop.
- Automatic updates in the cloud. Gambio's cloud plans include hosting and automatic updates; you can also host the shop yourself [3]. On your own hosting, a fix reaches your customers when you install the release that contains it.
You do not get:
- The new defaults in an existing shop. The withdrawal button that arrived in 26.05.0 is switched on by default only in newly set-up shops; existing shops set its visibility and styling themselves [7]. An older shop keeps its own StyleEdit colours, start-page content and theme copies in the same way.
- A maintained Honeygrid. Since 5.0.0.0 the release notes say of Honeygrid: "The theme is no longer being developed further!" [6]
- Accessible modules. Payment, shipping, review, filter and consent modules from third parties bring their own markup and scripts. Gambio's fixes cover Gambio's own templates.
- Useful alt text. The 4.9.5.0 fix covered the images on the default start page [4]. Product, category and banner images get their alt text from your product data or your import – or from nobody.
What we find on Gambio shops
Old themes and theme copies
Many shops run Honeygrid, a Malibu copy made before 2025 or a purchased theme. The fixes listed above live in the theme's templates. A theme that was copied or customised before those releases keeps the markup it was copied from, so a shop can be on a current version and still render the forms without <legend> and the quantity buttons without names.
StyleEdit colours and start-page widgets
StyleEdit lets you change the shop's design without writing code [3], including start-page widgets such as tabs and carousels [4]. It does not stop you from choosing light grey text on white, white text on a pastel button or a sale badge nobody can read. Start-page carousels often autoplay without a pause control, with unlabelled arrows.
Filters and category listings
The price filter, attribute filters and the switch between list and grid view are where keyboard and screen-reader users lose their place. Before 4.9.6.0, the filter's form groups had no <legend> and its roles were weaker [5]. Typical findings: a result list that reloads without announcing the new number of products, and focus that jumps back to the top.
Variants, quantity fields and configurators
Properties rendered as colour tiles, quantity steppers with "+" and "−" icons, and product configurators such as Gambio's GX-Customizer all need a name, a role and a state. Until 5.0.0.0 the quantity controls in the default theme had no names [6]. A delivery status shown only as a coloured icon tells a colour-blind customer nothing.
Buttons that only appear on hover
Until 26.05.0, the "Redeem" button for a voucher code in Malibu's basket only became visible when you hovered over the area [7]. The same pattern turns up in flyout menus, image zoom and tooltips: whatever needs a mouse is out of reach from a keyboard.
Checkout, payment modules and the withdrawal form
Payment iframes without a title, or with a broken focus order, end the purchase there. Texts that must be confirmed in the checkout, such as the notice on an item's condition, have been marked as required visually since 4.9.5.0 [4] – check that the requirement and the error message also reach assistive technology. And since 26.05.0 there is a new consumer-facing form: a login-free withdrawal form reached from a footer link [7]. In an existing shop you style it yourself, so its labels, errors and confirmation are yours to test.
Where to look first
| Criterion | Why on Gambio | Automation |
|---|---|---|
| 1.4.3 Contrast (Minimum) (AA) | StyleEdit colours, sale badges, footer links | Automated |
| 1.4.11 Non-text Contrast (AA) | Rating stars, input borders, filter tiles | Partly automated |
| 2.1.1 Keyboard (A) | Hover-only buttons, configurators, carousels | Partly automated |
| 1.4.13 Content on Hover or Focus (AA) | Flyout menus, image zoom, tooltips | Manual only |
| 2.4.7 Focus Visible (AA) | Theme CSS without a focus style | Partly automated |
| 4.1.2 Name, Role, Value (A) | Quantity steppers, icon buttons, variant tiles | Partly automated |
| 1.3.1 Info and Relationships (A) | Fieldsets without legend, filter groups | Partly automated |
| 4.1.3 Status Messages (AA) | Add to basket, filter results | Manual only |
| 3.3.1 Error Identification (A) | Checkout, registration, withdrawal form | Manual only |
| 1.1.1 Non-text Content (A) | Product and banner images | Partly automated |
"Automated" means a rule can decide the criterion on its own; "partly automated" means a rule finds some failures and a person has to judge the rest. The full list is in WCAG 2.2 AA, criterion by criterion.
A sensible order of work
- Know your version and your theme. Since March 2026 Gambio releases monthly as 26.x; the 4.x and 5.0 lines only get security updates until 31 December 2026 [8]. Plan the move now, in a test shop: Gambio warns that a master update can require changes to themes and modules [8].
- Compare against the stock theme. Scan a test shop once with an unmodified, current Malibu and once with your own theme. Whatever disappears came from your theme copy, your StyleEdit settings or your modules.
- Fix colours centrally. Contrast problems usually come from a handful of StyleEdit values. One change there clears a finding on every page – do the consent banner at the same time, since it is on every page too.
- Walk the purchase journey with a keyboard. Start page → category → filter → product → variant and quantity → basket with voucher → checkout → payment in test mode, and the withdrawal form. The start page alone tells you little.
- Inventory your modules. List every module with front-end output and decide for each one: patch it, replace it, or document it as a known limitation. Ask vendors for test evidence rather than a badge.
- Fix alt text at the source and re-test monthly. Put alt text into the product data or the import, not page by page, and crawl again after each monthly release.
What Reviseberg checks on Gambio – and what you still test yourself
Reviseberg crawls your shop, including category and product pages, and runs every axe-core rule on every page at a desktop width of 1280 pixels, then repeats the rules that change with the layout – contrast and target size among them – at 360 pixels. Results are mapped to WCAG 2.2 A/AA and EN 301 549. Findings are grouped into issues by rule and ranked by the points you gain by fixing them, so a defect in your theme shows up as one issue on 400 pages rather than 400 separate entries.
The keyboard agent opens the pages of a journey you name – a category page, a product page, the basket – and presses Tab, Shift+Tab and Escape through each of them, recording every step. It reports unreachable elements, lost or invisible focus, missing skip links and keyboard traps. It does not fill in forms or place an order, so the checkout steps behind a full basket, the payment iframe and the withdrawal form are yours to walk by hand. The free report covers up to 100 pages and runs the keyboard agent on one page you choose.
You still test some things yourself: whether alt text actually describes the image, whether error messages make sense, and how the shop behaves with a screen reader and zoom. Screen-reader, zoom and voice-control agents are not built yet; for those criteria the platform gives you guided manual tests, and a criterion nobody has tested is reported as untested, never as passed. There is no Gambio module from us, nothing is applied to your shop automatically, and we never inject an overlay script.
Written to be useful, not as legal advice. As of 27 September 2026.