How to fix presentation role conflict on Wix

Steps for Wix

1. Open the Wix Editor for your site. Identify the specific element flagged (use Chrome DevTools or axe to pinpoint it visually).
2. Click the element in the editor, open its Settings or Accessibility panel (the icon that looks like a person), and look for any custom ARIA label or role that has been set.
3. Remove any manually entered ARIA attributes that conflict with a presentational role.
4. For elements with role="presentation" set by Wix itself (e.g. decorative images), use the Image Settings panel and ensure the image is marked as 'Decorative' rather than given an alt text or label — Wix will then handle the role correctly.
5. If conflicting attributes were injected via Wix Velo (JavaScript), open the Velo Editor (Dev Mode) and search your page code for setAttribute calls setting role, aria-*, or tabindex, then resolve the conflict there.
6. Publish your site and re-scan with axe DevTools.

What is presentation role conflict?

When an HTML element is given `role="presentation"` or `role="none"`, it signals to screen readers: "ignore this element — it carries no meaning, it's only here for visual layout." However, if that same element also carries global ARIA attributes (like `aria-label`, `aria-describedby`, `aria-hidden`, etc.) or a `tabindex`, a direct conflict is created. The browser and screen reader receive two contradictory instructions at once: "treat this as meaningless" and "here's meaningful information about it." Different screen readers resolve this conflict differently — some honour the role and ignore the ARIA, others do the opposite — leading to unpredictable and broken experiences for assistive-technology users.

Screen reader users — including many shoppers who are blind or have low vision — may hear garbled, repeated, or missing announcements when navigating your store if this conflict exists on interactive or decorative elements. This directly harms conversions by making it harder to browse products, read descriptions, or complete checkout. Under WCAG 2.1 Success Criteria 4.1.2 (Name, Role, Value), this is a recognized failure that can create legal exposure under accessibility laws such as the ADA (US), EN 301 549 (EU), and the Equality Act (UK). Resolving it also improves your overall accessibility audit score, which is increasingly scrutinized in enterprise purchasing decisions and legal compliance reviews.

See the complete Presentation role conflict guide for every platform and the full background.