Wix accessibility and the EAA

What the Wizard covers, and what it can't reach

The Wizard is designed for exactly the class of issue it names: missing alt text, heading order, keyboard reachability, and generating a first-draft accessibility statement. What it can't do is evaluate things that depend on how a page is actually used — whether an error message on a form is announced to a screen reader, whether a custom-built accordion or tab component follows the correct ARIA pattern, or whether a color combination a designer picked in the editor meets WCAG's contrast ratio. Heavily customized Wix sites, and older sites built before the Wizard existed, routinely fail automated WCAG scans even after running it.

Where Wix sites usually still fail after the Wizard

In practice: custom-coded widgets or embedded third-party apps that the Wizard can't inspect, color and font choices made directly in the editor without checking contrast, and interactive elements (image galleries, lightboxes, sliders) that Wix's own template library ships in visually rich but not always fully keyboard-operable forms.

Does the EAA apply to a Wix site?

Yes, on the same basis as any other platform: if the site sells to or serves EU consumers and the business isn't a qualifying micro-enterprise, the EAA's requirements apply. Running the Accessibility Wizard is a reasonable first step, not a substitute for checking the result against WCAG 2.1 AA directly.

Other platforms