How to fix presentation role conflict on Adobe Commerce (Magento)

Steps for Adobe Commerce (Magento)

1. Identify the offending template file using Chrome DevTools → Elements panel. Note the surrounding HTML and any nearby Magento block or template hint comments (enable template hints via Stores → Configuration → Advanced → Developer → Debug → Enabled Template Path Hints).
2. Locate the corresponding .phtml template file in your custom theme directory: app/design/frontend/<Vendor>/<Theme>/.
3. Edit the file to remove the conflicting ARIA attribute or tabindex from the element that carries role="presentation" or role="none".
4. If the element is in a core or third-party module template, copy it to your theme directory first (following Magento's theme override pattern) rather than editing core files directly.
5. Run bin/magento cache:clean && bin/magento cache:flush from the CLI, then reload your storefront 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.