A Wix site is not accessible or inaccessible because it runs on Wix. Wix writes the HTML for every element and says itself that content and design are the site owner's responsibility [3]. So whether your Wix site is compliant depends on what you put on it and in which order – and on a few parts only Wix can change. This page separates the two.
Does the BFSG apply to your Wix site or shop?
If you sell to consumers with Wix Stores, or take bookings and payments online, you provide a "Dienstleistung im elektronischen Geschäftsverkehr" (§ 1(3) no. 5 BFSG), covered since 28 June 2025. The BFSG transposes the European Accessibility Act; other EU countries have equivalent laws [1][2].
Many Wix sites belong to very small businesses. 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; details are on our page on the micro-enterprise exemption. A shop that only sells to business customers is not a service to consumers.
Without a shop, it depends. The BFSG covers listed services – e-commerce, banking, telecoms, e-books, passenger transport – and a pure information site of a private company is generally not one of them; a booking or order function on it can be. Public bodies fall under BITV 2.0 instead. More in BFSG for online shops and the BFSG and EAA guide.
What the platform gives you, and what it does not
On Wix you work in an editor – the Wix Editor, the Studio Editor or the Wix Harmony Editor – and never touch the page's HTML. That decides what you can fix.
You get:
- Built-in basics. Wix states that its components are keyboard operable, show a focus ring for keyboard users and carry the correct semantics and ARIA attributes, and that pages get a "Skip to Content" link and the language you set [3].
- An automatic reading order. Wix sets the DOM order – the order in which the Tab key and screen readers move through a page – from the visual order of your elements. You can change it in the Layers panel [6].
- The Accessibility Wizard. It scans the site from the editor against WCAG 2.2 and splits its results into detected issues and manual tasks it cannot detect [4]. The Accessibility Monitor scans the live site and shows a status on the dashboard [5].
- Store settings that matter. For Wix Stores product pages, Wix recommends the Spotlight layout so a screen reader reads the page in a logical order [8]; in the checkout you set colours, fields and policies [9].
You do not get:
- Control over component markup. You cannot rewrite what a Wix button, menu or gallery renders. A defect inside a component is Wix's to fix; you can only choose another component or layout.
- A scan of everything. The wizard does not scan third-party apps, Velo code, the CMS, password-protected pages, side carts, checkout pages and several business solutions, among them Site Search, Reviews and Pricing Plans [4].
- Alt text or custom labels from your template. Wix's accessible templates bring a heading structure and colour contrast, but custom ARIA labels and alt text are not included and have to be added by hand [7].
- A compliance guarantee. Wix says it cannot guarantee compliance with regional law after using the wizard [4], and its accessibility page still cites WCAG 2.0 [3].
What we find on Wix sites
Freely placed elements, a different order
In the Wix Editor you can drop an element anywhere. The page looks tidy, but in the DOM a heading added last may sit after the text it introduces. The Tab key and screen readers follow the DOM, not what you see. After a redesign, check the order in the Layers panel and on the mobile view.
Headings picked for their size
Text themes make it tempting to pick "Heading 1" for any large text and a paragraph where a small heading looks better. The result: several H1s, skipped levels and section titles that are not headings – a wrong outline for anyone navigating by headings.
Cookie banners, apps and embeds
Apps from the App Market and anything pasted in as custom code bring their own markup, often in an iframe without a title: consent banners, chat, booking and review widgets. The wizard does not scan third-party apps [4], so a clean result says nothing about them. Test each with the keyboard: can you reach it, operate it and leave it again?
Store product pages and the side cart
On product pages, test colour and size options, quantity steppers and the image gallery. "Add to Cart" usually opens a side cart; if focus does not move into it and nothing is announced, a keyboard or screen-reader user never learns anything happened. The wizard does not scan side carts [4].
Slideshows and animation
Self-advancing slideshows, video backgrounds and scroll effects are one click away in the editor. Autoplay needs a pause control, arrows and dots need names, and lightboxes must close with Escape and return focus.
Forms, bookings and the checkout
Wix Forms, booking pages and the checkout carry the transaction. Check that every field has a visible label, that errors appear next to the field, and that the booking calendar works without a mouse. In the checkout, the essential fields and the structure are Wix's [9], and the wizard does not scan it [4]. Test it yourself; a problem you cannot change goes to Wix support and, until fixed, into your accessibility information as a known limitation.
Where to look first
| Criterion | Why on Wix | Automation |
|---|---|---|
| 1.3.2 Meaningful Sequence (A) | Freely placed elements, DOM order | Manual only |
| 2.4.3 Focus Order (A) | Side cart, lightboxes, mobile menu | Partly automated |
| 1.3.1 Info and Relationships (A) | Headings chosen by size | Partly automated |
| 1.1.1 Non-text Content (A) | Product media, galleries, logo | Partly automated |
| 1.4.3 Contrast (Minimum) (AA) | Theme colours, text over images | Automated |
| 4.1.2 Name, Role, Value (A) | App widgets, HTML embeds, icon buttons | Partly automated |
| 2.2.2 Pause, Stop, Hide (A) | Self-advancing slideshows, video backgrounds | Partly automated |
| 4.1.3 Status Messages (AA) | "Add to Cart", side cart | Manual only |
| 3.3.1 Error Identification (A) | Wix Forms, bookings, checkout | Manual only |
"Automated": a rule decides the criterion alone. "Partly automated": a rule finds some failures, a person judges the rest. All criteria: WCAG 2.2 AA, criterion by criterion.
A sensible order of work
- Run the Accessibility Wizard, then list what it skipped. Fix what it detects, work through its manual tasks, and note the parts it does not scan: apps, side cart, checkout, Velo pages [4].
- Settle the site-wide settings once. Site language, theme colours and text themes apply everywhere; one change clears a finding on every page.
- Check the order of every template page. Use the Layers panel after each layout change, and look at the mobile view separately [6].
- Write alt text at the source. In image settings, galleries and each store product's media.
- Inventory your apps and embeds. Test each with a keyboard, then keep, replace or document it as a known limitation. Do not add a toolbar to cover gaps; Wix says toolbars are not needed to meet WCAG [10].
- Walk the purchase or booking by hand, and re-check after publishing. Product → option → cart → checkout, or service → date → form. Wix recommends checking the Monitor after each publish [5].
What Reviseberg checks on Wix – and what you still test yourself
Reviseberg crawls your published site, store pages included, 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 header or in a Wix component is one issue, not dozens. Where the cause sits in markup only Wix can change, you mark the issue "can't fix" with a reason, and it stays on record.
Reviseberg reads the rendered pages, so it also sees the apps the wizard leaves out. The keyboard agent opens the pages of a journey you name – say a product page and a booking page – 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, book or pay, so the side cart after "Add to Cart" and the checkout 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 describes the image, whether error messages make sense, and how the site 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. We offer no Wix app, install nothing on your site and never inject an overlay script.
Written to be useful, not as legal advice. As of 27 September 2026.