Wix has invested more in accessibility than most website builders, and that's genuinely good news if you run a site there. But "Wix has accessibility features" and "my Wix site is accessible" are two very different statements. The platform gives you a strong foundation and some real tools, then leaves the decisions that matter most to you.
This guide cuts through the marketing. It explains exactly what Wix accessibility tooling does, where it quietly stops helping, and the specific manual checks that decide whether a disabled visitor can actually use your site. If you're aiming for WCAG 2.2 Level AA — the bar set by the European Accessibility Act — this is where to focus.
What Wix gives you out of the box
Wix sites start with a better accessibility baseline than a hand-coded site that nobody thought about. The platform ships several things automatically, and it's worth knowing what they actually cover.
- Semantic structure on standard elements. Wix headers, footers, and navigation menus render with the right landmark roles, and its menu component is keyboard-operable by default.
- A visible focus indicator. Keyboard users see an outline as they tab through the page — a requirement (WCAG 2.4.7) that countless custom sites fail.
- Skip-to-content links and heading-order tools. The editor lets you mark which text is an H1, H2, and so on, and exposes a 'main' landmark so screen-reader users can jump past the menu.
- An accessibility settings panel. Wix can detect the visitor's operating-system preferences and respect reduced-motion settings, dimming animations for people who get motion sickness.
None of this is nothing. A Wix site you never touch is usually more accessible than a custom site nobody maintained. The catch is that these defaults only protect the parts of your site Wix controls — and you control most of what matters.
The Accessibility Wizard: useful, but not a finish line
Wix's flagship tool is the Accessibility Wizard, found in the editor under Settings. It scans your pages and walks you through fixes: flagging images missing alternative text, headings that skip levels, and elements with poor colour contrast. For a site owner with no accessibility background, it's a genuinely good starting point and catches the most common, embarrassing mistakes.
Here's the limit nobody tells you. The Wizard is a guided checklist, not a guarantee. It can tell you an image has no alt text, but not whether the alt text you wrote is correct — 'image123.jpg' technically passes. It flags low contrast on text it can measure, but it can't evaluate text sitting on a background photo or a gradient, which is where most contrast failures actually live. And it only inspects the pages and states it can see, so a dropdown that opens on click, or a pop-up that loads later, often goes unchecked.
Treat the Wizard as step one. Clearing it means you've handled the obvious machine-detectable issues — which, across the whole web, are only a fraction of real accessibility barriers.
Where Wix accessibility quietly falls short
The gaps aren't Wix being careless — they're the parts of accessibility that depend on human judgement and on choices you make in the editor. These are the recurring problems on real Wix sites:
- Custom-designed elements lose their semantics. When you build a 'button' out of a styled text box or a shape with a link, screen readers may announce it as plain text, and keyboard users may not be able to reach it. Use Wix's actual Button element, not a box that looks like one.
- Drag-and-drop breaks reading order. Wix lets you place elements anywhere, but a screen reader follows the underlying DOM, not the visual layout. An element you dragged to the top can be read last. Check this with the Wizard's reading-order tool on every page.
- Images of text and decorative images. A promo banner with text baked into the image is invisible to screen readers and unreadable when zoomed. Decorative images, meanwhile, need empty alt text so they're skipped — not a filename.
- Third-party apps from the Wix App Market. Booking widgets, chat bubbles, galleries, and pop-ups are built by other developers. Their accessibility is largely out of Wix's hands, and many are not keyboard-operable.
- Wix Velo and custom code. Anything you build with custom code bypasses the platform's safety rails — accessibility is then entirely your responsibility.
The manual checks every Wix site owner should run
After the Accessibility Wizard, these five checks find the issues automation can't. None require technical skill — just a few minutes per page.
- Keyboard test. Unplug your mouse. Press Tab through the whole page. Can you reach every link, button, and form field, in a sensible order, and see where you are? Can you open and close every menu and pop-up? See our keyboard accessibility guide for what to look for.
- Contrast on real backgrounds. Check text over photos, gradients, and coloured buttons. Body text needs a 4.5:1 ratio; large text (18pt, or 14pt bold) and icons need 3:1. Our colour contrast guide explains how to measure it.
- Alt text quality. Read your alt text aloud. Does it describe what the image conveys, or is it a filename? Our guide to writing alt text shows the difference.
- Forms. Every field needs a visible, programmatically linked label — placeholder text alone doesn't count — and error messages must say what went wrong in words.
- Zoom to 200%. Browser-zoom your page. Does anything get cut off, overlap, or require horizontal scrolling? Reflow is a common Wix failure on image-heavy layouts.
To turn this into a repeatable process, work through our accessibility checklist and confirm the machine-detectable layer first with a free accessibility scan.
Wix and legal compliance (EAA, WCAG, EN 301 549)
If you sell to consumers in the EU, the European Accessibility Act has applied since 28 June 2025. The standard it points to is WCAG 2.2 Level A and AA, referenced through the European standard EN 301 549. Using Wix does not make you compliant by itself — the platform's tools help you reach that bar, but the responsibility for meeting it sits with you, the site owner.
WCAG is built on four principles — content must be Perceivable, Operable, Understandable, and Robust — and the failures above map directly onto them: missing alt text fails Perceivable, an unreachable custom button fails Operable. Microenterprises that provide services (fewer than 10 staff and under €2,000,000 annual turnover) are largely exempt for services, but most growing businesses are not. Penalties are set nationally, so fines vary by member state and can reach tens of thousands of euros. To document your conformance, create one with our accessibility statement generator. On another platform? We also have guides for WordPress and Shopify.