Accessibility on a Wix site comes down to a short list of things that go wrong over and over: images without a description, headings used for size instead of structure, light grey text on white, "Read more" links, form fields without labels. None of them needs code. This checklist says what each one is, how to check it, and where in Wix to fix it.
It is a starting point, not a certificate. Automated checks — Wix's and anyone else's — find only part of the problems a site can have, and nothing on this page makes a site "compliant" by itself.
Who needs to care
- Selling to people in the EU. The European Accessibility Act has applied since 28 June 2025 to many online services sold to consumers, including e-commerce, and to companies outside the EU that sell into it. It points to the harmonised standard EN 301 549, which is built on WCAG. Very small service businesses (fewer than 10 staff and no more than €2 million turnover) are exempt, but check what applies to you with a lawyer, not a blog.
- Everyone else. Roughly the same fixes make a site easier to use on a phone, in sunlight, with a broken arm or with tired eyes. They also help search engines understand your pages.
The target most guides use is WCAG 2.2 level AA.
Start with Wix's Accessibility Wizard
Wix has a free built-in checker: in the Editor, open Settings → Accessibility Wizard. According toWix's help article, it checks colour contrast in containers, heading tags, linked text, alt text, ARIA attributes on images, and repeated issues. Run it first; it fixes the most common problems in place.
What it doesn't do:
- It runs in the Editor, page by page. It doesn't load the published site the way a visitor's browser does, at desktop and phone sizes.
- It doesn't watch the site. A new page or a new product next month isn't checked until you run it again.
- It can see that alt text exists, not whether it describes the image.
The checklist
1. Every meaningful image has alt text
Alt text is what a screen reader says instead of the image. Describe what the image shows and why it's there: "Black leather tote bag, front view", not "IMG_2031" or "image".
- Where: click the image → Settings → "What's in the image? Tell Google". Product images: Wix Stores → product → image settings.
- Decorative images (background textures, dividers) should be marked decorative so screen readers skip them.
2. One H1 per page, then headings in order
Screen reader users jump between headings like a table of contents. Use H1 once for the page title, H2 for sections, H3 inside them. Don't pick a heading level for its size — change the size in the text theme instead.
- Where: select the text → the text style dropdown → choose Heading 1–6 or Paragraph.
3. Text contrast of at least 4.5:1
Normal text needs a contrast ratio of 4.5:1 against its background; large text 3:1. Light grey on white and white on pastel photos are the usual failures. Text over images is the hardest: add a solid or semi-transparent strip behind it.
4. Links say where they go
"Read more", "Click here" and "Learn more" make no sense when a screen reader lists all links on a page. Write "Read our returns policy" or "See all summer dresses".
5. Every form field has a label
Placeholder text disappears when you type and isn't a label. Turn on field titles in Wix Forms, and make error messages say what's wrong ("Enter an email address like name@example.com").
6. Everything works with a keyboard
Press Tab from the top of your page. You should see where you are at every step (a visible focus outline), reach the menu, every link and button, the cart and the checkout, and be able to close any popup with Esc.
7. Nothing moves, flashes or plays by itself — or it can be stopped
Auto-playing video with sound, endless sliders and flashing elements are a problem for people with vestibular disorders, epilepsy or attention difficulties. Turn autoplay off or add a pause control.
8. The phone layout gets the same care
Wix keeps a separate mobile layout. Hidden elements, overlapping text and tiny buttons often exist only there. Check it in the mobile editor and on a real phone, and make buttons at least 44 × 44 pixels.
9. An accessibility statement
A short page that says what you've done, what you know isn't accessible yet, and how a visitor can reach you if something doesn't work. Link it from the footer. Don't claim the site is "fully compliant".
What an accessibility widget does and doesn't do
A widget lets each visitor adjust the page for themselves: bigger text, more spacing, higher contrast, stopping animations. That's genuinely useful. It doesn't add missing alt text, fix your headings or label your forms, and it doesn't make a site compliant on its own. We explain why indo accessibility widgets make a Wix site compliant?
Checking your whole site with Aislekind
Aislekind for Wix does both halves. The scanner opens your published pages in a real browser, on desktop and phone sizes, checks them against WCAG 2.2 AA with axe-core, and lists each problem in plain language with a screenshot of the element and who fixes it: you in the Wix Editor or the Accessibility Wizard, or Wix itself for markup it generates. The free plan scans 20 pages; Pro scans 100 and re-scans weekly. The visitor widget is complete on every plan, adds no accessibility errors of its own, and keeps visitors' choices in their own browser.
Neither the scan nor the widget makes a site compliant by itself. They show you what to fix and help visitors in the meantime.