How to fix aria command name on Squarespace

Steps for Squarespace

1. Log in to your Squarespace account and go to Website → Pages or Design → Custom CSS.
2. For icon-only buttons built with Squarespace blocks (e.g., social icons, navigation buttons), Squarespace auto-generates some labels but may miss custom icon blocks.
3. Go to Pages → select the page → click Edit → click the flagged block/element → open its block settings and fill in the 'Description', 'Alt text', or 'Button label' field if available.
4. For site-wide elements like the cart icon or mobile nav toggle that are part of the theme and not directly editable in the block editor, go to Design → Custom CSS and inject a CSS-based visually-hidden label workaround, OR use Settings → Advanced → Code Injection to add a small JavaScript snippet that sets `aria-label` on those elements after the page loads (see code snippet below).
5. Re-publish and test with axe to confirm the label appears.

What is aria command name?

The `aria-command-name` rule flags interactive elements — specifically buttons (`role="button"`), links (`role="link"`), and menuitems (`role="menuitem"`) — that have no accessible name. An "accessible name" is the text a screen reader reads aloud when a user lands on that element. It can come from visible text inside the element, an `aria-label` attribute, an `aria-labelledby` attribute pointing to another element's text, or (for images used as buttons) a meaningful `alt` attribute. When none of those exist, the screen reader either reads nothing at all or reads something meaningless like the raw URL or a string of punctuation, leaving visually impaired shoppers completely in the dark about what the control does.

WCAG 2.1 Success Criterion 4.1.2 (Name, Role, Value) is a Level AA requirement, meaning it is referenced in most accessibility laws worldwide — including the ADA (US), EN 301 549 (EU), AODA (Canada), and EAA (UK/Europe). Failing it exposes your store to legal complaints and demand letters that are increasingly common against ecommerce sites. Beyond legal risk, blind and low-vision shoppers using screen readers simply cannot use controls without accessible names — they cannot add items to a cart, navigate menus, or complete a purchase — directly costing you revenue and customers. Additionally, Google uses accessibility signals as one of many quality indicators, so a more accessible site can support better crawlability and user experience scores.

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