Wix's Auto-Generated Alt Text Isn't Enough — Here's What's Actually Missing

What Wix's Accessibility Wizard Actually Covers (And What It Misses)

Wix added an accessibility wizard in 2020 and has improved it since. Credit where it's due: it addresses more than most drag-and-drop builders. But the wizard was designed to catch the most obvious structural issues — and it doesn't address several violation types that plaintiff scanners specifically target.

Issue	Wix Wizard	Your Action Required
Skip navigation link	Covered	Enable in wizard → Keyboard Navigation
Focus indicators on interactive elements	Covered	Enable in wizard → Visual Focus Indicators
Color contrast in Wix templates	Partial	Wizard checks template defaults; custom sections and strips are not checked
Alt text for images	Partial	AI generates generic text; you must write descriptive alt text manually for meaningful images
Form field labels	Gap	Wix forms use placeholder-only labels by default; must add labels in form settings
Drag-drop element focus traps	Gap	Overlapping elements and popups must be fixed manually in the editor
Mobile tab order	Gap	Mobile editor changes can break desktop tab order; must check and fix in accessibility panel
Lightbox/popup keyboard behavior	Gap	Wix lightboxes don't trap focus or support Escape to close by default

The 5 Violations to Fix in Wix Editor

Violation 1: Auto-generated alt text that's generic or meaningless

Wix's AI describes images with phrases like "a person standing near a building" or outputs the filename as alt text. Both are WCAG 1.1.1 failures: screen reader users hear a description that doesn't convey the actual purpose or content of the image.

Descriptive alt text answers the question: if the image didn't load, what information would a visitor be missing? For a product image: what it looks like, relevant attributes. For a hero image of a business: what it shows and why it matters.

Fix in Wix Editor (no code needed):

1. 1
   Open EditorClick any image on your page in Wix Editor to select it.
2. 2
   Settings panelClick the settings icon (gear) in the toolbar that appears above the image.
3. 3
   Alt text fieldFind the "Alt Text" field. Delete any auto-generated text. Write a specific description: instead of "image of flowers" write "Peony bouquet in blush pink and white, arranged in a glass vase."
4. 4
   Decorative imagesFor purely decorative images (backgrounds, dividers, icons that duplicate nearby text), leave the alt text field empty — Wix will output alt="", which tells screen readers to skip it.

For Wix Stores product images: go to the Wix Dashboard → Store Products → select a product → click any product image → "Image Settings" → update the alt text field. This applies to all pages where that product image appears.

Violation 2: Wix form fields using placeholder-only labels

Wix's default form fields display placeholder text inside the input box ("Enter your name"). When users click the field, the placeholder disappears and there's no visible or accessible label telling them what to type. This fails WCAG 1.3.1 (Info and Relationships) and 3.3.2 (Labels or Instructions).

Wix has a form label setting that most users never enable:

1. 1
   Select formClick your form element in Wix Editor to select it.
2. 2
   Open settingsClick the "Settings" button in the blue toolbar (not the layout button).
3. 3
   Field settingsClick the pencil icon next to any field to edit it individually.
4. 4
   Label positionUnder "Label," set the position to "Above input" or "Side by side." This makes the label visible above the field at all times — not just as a placeholder that disappears.
5. 5
   Repeat for all fieldsDo this for every field in the form: name, email, phone, message, etc.

Violation 3: Drag-and-drop elements creating keyboard focus traps

Wix's drag-and-drop editor lets you layer elements on top of each other — decorative boxes, image overlays, popup triggers. When elements overlap in a way that places a non-interactive element in the keyboard tab order, it creates a focus trap: keyboard users get stuck tabbing through invisible or non-functional elements.

The most common cause is a transparent overlay box or strip placed on top of a button or link for visual styling. The overlay intercepts clicks but isn't keyboard-accessible.

How to detect focus traps on your Wix site:

1. 1
   Publish your siteOpen the live published URL (not the editor preview).
2. 2
   Tab through the pagePress Tab repeatedly from the top of the page. Every interactive element (links, buttons, form fields) should receive a visible focus outline as you tab through.
3. 3
   Identify stuck pointsIf you can't reach an element by Tab, or if Tab stops moving forward, you've found a focus trap or missing focusable element.
4. 4
   Fix in editorSelect the overlapping element in Wix Editor. In the element settings, check "Hidden from screen readers" if it's purely decorative. For transparent overlay boxes, delete them and use Wix's native layer styling instead.

Violation 4: Mobile editor changes breaking desktop tab order

Wix has separate mobile and desktop editors. A common accessibility mistake: you hide an element in the mobile editor by moving it off-screen or setting it to invisible. In the published site, this sometimes affects the element's position in the accessibility tree — creating a reading order that jumps around unpredictably for screen reader users on desktop.

Fix the tab order using Wix's Accessibility Panel:

1. 1
   Open Accessibility PanelIn Wix Editor → click the Accessibility icon in the left sidebar (person with circle). This opens the accessibility panel.
2. 2
   Tab Order viewClick "Tab Order" to see a list of all focusable elements on the page in the order keyboard users will encounter them.
3. 3
   Reorder if neededDrag elements in the panel to reorder the tab sequence. The visual order on screen should match the logical reading order: top-to-bottom, left-to-right for the main content areas.
4. 4
   Check mobile separatelySwitch to the mobile editor and verify the mobile tab order independently. Hiding or repositioning elements in mobile should not use workarounds that affect the DOM order.

Violation 5: Wix lightboxes not managing keyboard focus

Wix's built-in lightbox elements (used for popups, galleries, promotions) have a structural accessibility gap: when a lightbox opens, keyboard focus stays on the element that triggered it — not inside the lightbox. Screen reader users can't navigate the lightbox content. Users can't close it with Escape. This fails WCAG 2.1.2 (No Keyboard Trap) and 4.1.2 (Name, Role, Value).

This is one case where Wix Velo (Wix's JavaScript development layer) is the right tool:

Once Velo is enabled, open the Page Code panel (not Site Code) for the page with your lightbox:

// Wix Velo: fix lightbox keyboard behavior
// Replace 'myLightbox' with the actual ID of your lightbox element

import wixWindow from 'wix-window';

$w.onReady(function () {
  // Track what was focused before opening
  let lastFocused;

  $w('#openLightboxBtn').onClick(() => {
    lastFocused = document.activeElement;
    wixWindow.openLightbox('myLightbox');
  });

  // Handle Escape key to close lightbox
  document.addEventListener('keydown', (e) => {
    if (e.key === 'Escape') {
      wixWindow.lightbox.close();
      if (lastFocused) lastFocused.focus();
    }
  });
});

For simpler lightbox setups — a promotional popup that fires on page load — the minimum fix is to ensure the lightbox has a visible, keyboard-accessible close button with an aria-label set via the element's Accessibility settings in the editor. Select the close button → Settings → Accessibility → "Screen Reader Label" → type "Close dialog."

ADI vs. Wix Editor: Compliance Comparison

If you're not sure which editor your site uses, check: in your Wix dashboard, if you see "Edit Site" → Editor, you're using Wix Editor. If you see limited editing options and were created via ADI, you're likely on ADI.

Feature	Wix Editor	Wix ADI
Accessibility panel + tab order control	Available	Not available
Alt text editing per image	Available	Limited
Form label settings	Available	Not available
Velo custom JavaScript	Available	Not available
Accessibility wizard	Available	Not available

Bottom line: If you're on ADI and concerned about ADA compliance, convert to Wix Editor. It's the only way to access the tools needed to fix the violations described in this guide.

Quick Implementation Checklist for Wix Site Owners

• 1
  Run the Wix accessibility wizard first. Editor → Accessibility → Accessibility Wizard. Enable keyboard navigation, visual focus indicators, and skip to content. This covers the basics in a few clicks.
• 2
  Scan your live site with ADAFlags. Run a free scan on your homepage, a product or service page, and your contact page. This tells you exactly which violations remain after the wizard.
• 3
  Write real alt text for every meaningful image. Click each image → Settings → Alt Text. Delete auto-generated descriptions. Write specific, descriptive text. Leave decorative images empty.
• 4
  Fix form labels. Select each form → Settings → edit each field → set Label position to "Above input." This makes labels permanently visible, not just as placeholder text.
• 5
  Check and fix tab order. Editor → Accessibility Panel → Tab Order. Verify keyboard users will encounter elements in a logical sequence. Fix any out-of-order elements by dragging in the panel.
• 6
  Fix lightbox keyboard behavior. If you have popups or lightboxes: ensure there's a visible close button with an "aria-label" of "Close dialog." For advanced fix, use Velo to add Escape key support and focus management.
• 7
  Re-scan after changes. Run ADAFlags again to confirm violations are resolved. Save the scan results as documentation of your remediation effort.

Frequently Asked Questions

Does Wix's built-in accessibility wizard make my site ADA compliant?

No. Wix's accessibility wizard addresses some common issues — color contrast, skip navigation, and focus indicators — but it doesn't cover auto-generated alt text gaps, drag-and-drop focus traps, mobile tab order problems, or custom form labels. Running the wizard is a good starting point, but it doesn't constitute compliance.

Is Wix's auto-generated alt text enough for ADA compliance?

No. Wix's AI generates generic alt text — descriptions like "a person standing near a building" or file names. Plaintiff scanners test whether alt text is meaningful and descriptive. Generic or filename-based alt text is flagged as a WCAG 1.1.1 failure the same as an empty attribute. You need to write descriptive alt text for every significant image.

Can Wix ADI sites be ADA compliant?

ADI sites have limited customization — you cannot access the accessibility panel or modify individual element properties. To achieve actual compliance, convert to Wix Editor (free, irreversible) and apply the fixes in this guide. The conversion preserves your content but replaces the limited ADI editing interface with the full Editor.

What is Wix Velo and when do I need it for ADA compliance?

Wix Velo is Wix's JavaScript development platform — free to enable, no setup required. For most ADA compliance issues, you don't need it: editor-level fixes cover the major violations. Velo is useful for advanced scenarios: keyboard focus management in lightboxes, programmatic aria-live announcements, and custom keyboard handlers. Enable it under Site → Turn on Dev Mode.

What are the most common ADA violations on Wix sites?

Auto-generated alt text that's generic or missing for meaningful images, form fields using placeholder-only labels, drag-and-drop element overlaps creating keyboard focus traps, mobile editor changes that break tab order on desktop, and lightboxes that don't support Escape key or manage keyboard focus properly. These five patterns appear in Wix ADA demand letters.

Related reading: Comparing overlay tools? Best AccessiBe Alternatives · UserWay Alternatives · AudioEye Alternatives. Other platform guides: Shopify ADA Compliance · WordPress ADA Compliance. Full legal picture: 2025 ADA Lawsuit Tracker (141 defendants).