The Wix Accessibility Wizard: What It Finds and What It Cannot

Run the Wizard and it scans your site, then reports in two tabs: Detected issues and Manual tasks.

Detected issues split into two kinds. Site-level problems cover things that apply across the whole site, including the main language setting and DOM order. Page-level problems cover the content of individual pages — missing alternative text, insufficient colour contrast. Usefully, it reaches into pages generated by Wix's own business solutions, including Stores and Blog, which is more than you get from pointing a browser extension at your home page.

It references WCAG 2.2, which is the current W3C Recommendation, updated 12 December 2024. That is a more current reference point than several competing tools use.

The manual tasks tab is the other half, and it is the half that matters. It lists the things the Wizard cannot detect and hands them back to you with guidance: use of colour, text baked into images, whether zoomed content still works, media alternatives, and the accessibility statement itself.

This is the part that should shape how you use the tool. From Wix's help centre:

we cannot guarantee that your site will be compliant with your region's accessibility laws and regulations after using the Wizard

It is worth pausing on. A vendor with every commercial reason to let you believe otherwise has written down that running its tool does not settle your obligation, and recommends consulting an accessibility expert for your region.

That sentence is the most useful thing in the Wizard's documentation, and it is one reason Wix scores as well as it does here. A platform that tells you where its tool stops changes what you do next.

Two categories, and they are not equally obvious.

Presence versus meaning

The Wizard can see that an alt attribute is missing. It cannot see that the one you wrote says banner-final-2. SC 1.1.1 Non-text Content asks for text that serves an equivalent purpose to the image, and "an attribute exists" is not the same claim. Every automated tool in existence shares this limit; the difference is whether the product is honest about it, and this one is.

The same gap covers heading structure. A scanner can flag a skipped level. It cannot tell you that your headings describe the page's sections in a way that makes navigating by heading useful, which is the actual point of SC 1.3.1.

The editor is not the site

The Wizard assesses your published site. It does not tell you whether the site is operable, because operability is a behaviour rather than a property of the markup. Tab through your own Wix site and see whether the focus indicator survives your theme customisations, whether the mobile menu can be opened and closed from the keyboard, and whether a popup returns focus somewhere sensible. That is the keyboard test and it is the necessary companion to any scan.

1. Run it early, not at launch. Fixing DOM order and heading structure after a site is built is considerably more work than doing it as you go.
2. Treat the manual tasks tab as the real list. The detected tab is triage; the manual tab is the work.
3. Re-run it after every significant change. Adding a store, an app or a new template changes the surface area, and the Wizard reaching into app pages is precisely why this is worth doing.
4. Follow it with a keyboard pass. The Wizard and the keyboard test catch almost entirely different things.
5. Do not treat a clean report as an answer. It means the automatically detectable problems are handled, which is a genuine achievement and not the same as the site being good.

Wix's Wizard is the most substantial accessibility tooling of any mainstream builder in this comparison, and having a scanner that finds problems inside app-generated pages is a real advantage over platforms that offer nothing.

What it does not do — and what Wix does not claim it does — is settle anything. It cannot judge meaning, it cannot test operation, and it cannot make a legal determination, which nothing on this site is qualified to do either. Used as triage, followed by a keyboard pass and honest writing, it is a real head start. Used as a certificate, it is a way of feeling finished while a large part of the work has not been done.

Where Wix sits against the other platforms is set out in the assessment of ADA-compliant website builders, along with what none of them can do for you.