How to fix presentation role conflict on Squarespace

Steps for Squarespace

1. In Squarespace, direct HTML editing is limited. Start by identifying which element triggers the issue using Chrome DevTools → Elements panel.
2. If the element is a built-in Squarespace block (e.g. a decorative image or spacer block), check whether a custom Code Block or CSS injection is adding ARIA attributes — go to Pages → (your page) and look for any Code Blocks, or check Design → Custom CSS.
3. Remove or correct any custom ARIA attributes in the offending Code Block or Custom CSS/JS injection under Settings → Advanced → Code Injection (header/footer).
4. If the issue is in Squarespace's own theme output and you cannot edit it directly, document the element and submit a support request to Squarespace, or use the Code Injection area to inject a small corrective JavaScript snippet that removes the conflicting attribute after DOM load (see code snippet below).
5. Republish 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.