Make your Wix site truly accessible. EAA & WCAG, without an overlay

The truth: Wix is not accessible by default

Wix has shipped cleaner default markup in recent years than it used to, but rarely meets WCAG 2.2 AA on its own. Because you can barely reach the generated code and the editor decides the order for you, barriers appear that your visitors, and the European Accessibility Act, won't accept.

What commonly goes wrong on Wix

• Repeaters without semantic structureA Wix repeater visually repeats the same block, but often outputs a flat row of divs with no list or region structure. A screen reader then hears separate items without knowing they form one connected list.
• Drag-and-drop yields illogical focus orderBecause you drag elements freely onto the canvas, the reading and focus order follows the spot in the code, not what you see on screen. Keyboard users end up jumping around the page at random.
• Icon buttons without a nameMenu, cart and social icons are often added in Wix as an image or shape with no text. Without an aria-label a screen-reader user hears only 'button' or 'image' and has no idea what the action does.
• Aria only addable through VeloFor many elements the editor offers no field for aria attributes. To add a role or accessible name, you often have to use Velo or a custom embed, something most Wix sites never do.

What a real fix looks like

Take an icon button on your Wix site. Without an accessible name, a screen-reader user only hears 'button'. Through Velo you give the element an aria-label, no rebuild:

// Icoon-knop zonder naam, alleen een afbeelding

$w.onReady(() => {
  $w('#cartIcon').accessibility.ariaAttributes.label = 'Winkelwagen';
});

What you get

With a reporting tool you pay the licence and your developers to fix the issues. With Seviranta the fix is included, no double bill.

Protect your conversion and your legal standing

An app that slaps an accessibility icon over your Wix site is a risk to your business. The facts:

Is the Wix Accessibility Wizard enough for the EAA?

No. The Wizard is a good first step, but it skips the checkout, third-party apps, CMS content and Velo, and does not measure everything WCAG requires. A regulator tests the live page. Run the Wizard, then scan the published site.

I also sell to Germany or France. What applies to my Wix store there?

Germany: the BFSG has applied to B2C online stores since 28 June 2025, with an exemption for micro-enterprises (fewer than ten people and at most 2 million euros in turnover or balance sheet total); supervision by the Marktüberwachungsstelle der Länder (MLBF). France: since 28 June 2025 e-commerce falls under the EAA transposition in the Code de la consommation, with the same micro-enterprise exemption, supervised by the DGCCRF; the yardstick is the RGAA (WCAG 2.1 AA). In both countries the published page counts, not the fact that you use Wix.

What can I do when a finding sits inside a Wix app or the checkout?

What sits inside a Wix app or the Wix checkout cannot be repaired in code by you. Our report names exactly which element and which rule it is, so you can report it to Wix or the app maker, choose an alternative and document what you did. That dated record is what a regulator wants to see.

Is a Wix accessibility widget enough for the EAA?

No. A widget puts a layer over your site, but doesn't repair the underlying code and doesn't count as structural compliance.

Does my Wix checkout fall under the EAA?

Yes. The checkout and navigation are explicitly part of the obligation under WCAG 2.1 AA.

Does Seviranta also scan my Wix apps?

Yes. We test the final generated HTML, theme plus apps, the way a regulator does.

Will this slow my Wix site down?

No. We scan externally from our EU servers; no script goes on your site. 0% impact on your load speed and Core Web Vitals.