How to fix aria roles on Squarespace

Steps for Squarespace

1. Squarespace does not allow direct HTML editing of structural templates; invalid roles in core blocks must be reported to Squarespace Support.
2. For roles inside Code Blocks or custom HTML you added yourself: in the Page Editor, click the Code Block, select Edit, find the `role=` attribute in your markup, correct it, and save.
3. For site-wide custom code (e.g. injected via Settings → Advanced → Code Injection): go to Settings → Advanced → Code Injection, locate the snippet containing the invalid role, correct it, and save.
4. Republish and verify with an axe browser extension on the live page.

What is aria roles?

The `role` attribute tells assistive technologies (screen readers, braille displays, voice control software) what kind of interface element something is — for example, a button, a navigation landmark, a dialog, or a list. The WAI-ARIA specification defines an exact list of allowed role names. If any element on your store carries a role that isn't on that list — whether it's a typo like `role="buton"`, an invented name like `role="product-card"`, or an outdated value like `role="presentation"` used incorrectly — the browser and screen reader simply ignore it or misinterpret the element entirely. WCAG Success Criterion 4.1.2 (Name, Role, Value) requires that every user interface component exposes a valid, programmatically determinable role so all users can understand and operate it.

Screen reader users — who include people with visual impairments, motor disabilities, and cognitive disabilities — rely on role information to navigate and interact with your store. An invalid role means those customers hear confusing or missing announcements, cannot identify interactive controls, and may abandon your checkout or product pages. Beyond lost conversions, accessibility failures carry real legal risk: WCAG 2.1 AA compliance is referenced in ADA Title III lawsuits and, in many jurisdictions, is a statutory requirement for online businesses. Google also uses accessibility signals as a quality factor, so pages riddled with invalid ARIA can indirectly suppress organic rankings. Fixing invalid roles is typically a quick code change with outsized impact on both compliance and customer experience.

See the complete Aria roles guide for every platform and the full background.