How to fix error not associated on Squarespace

Steps for Squarespace

1. Log in to your Squarespace dashboard and open the page containing the form block.
2. Click the form block → Edit → Form tab: ensure every required field has a meaningful field label (this becomes the error reference).
3. Squarespace's native form blocks have limited ARIA customisation. To inject aria-invalid and aria-describedby, go to Website → Pages → select the page → click the </> icon (Page Header Code Injection) or use Settings → Advanced → Code Injection (site-wide).
4. In the Code Injection footer, add a <script> block that listens for the form's submit event, validates fields, and programmatically sets aria-invalid and inserts/updates a sibling <span id="FIELDNAME-error"> with the error text.
5. Alternatively, embed a fully accessible third-party form (e.g. Tally, Typeform accessible mode, or a hand-coded HTML form) via an Embed Block for complete control over ARIA markup.
6. Save and test with a screen reader.

What is error not associated?

When a customer fills out a form on your site (checkout, contact, newsletter sign-up) and submits it with a mistake, your site needs to tell them two things: (1) that the field is in an error state, and (2) what the error actually is. Sighted users see this visually — a red border, an error message below the field. But screen reader users rely on invisible HTML attributes called `aria-invalid` and `aria-describedby` to receive the same information. Without these attributes, a screen reader user hits Submit, nothing seems to happen, and they have no idea which field failed or why. WCAG 2.1 Success Criterion 3.3.1 (Error Identification) requires that input errors be identified and described to the user in text.

Roughly 7–8 million people in the US use screen readers, and many more use other assistive technologies. If your checkout or contact form is inaccessible, these customers simply cannot complete a purchase or inquiry — which is lost revenue you may not even know about. Beyond conversions, the ADA and similar laws in many countries treat web accessibility failures as discrimination, creating legal exposure including demand letters and lawsuits that have cost retailers thousands to hundreds of thousands of dollars to resolve. Fixing form error accessibility is also a direct ranking signal for Google's Core Web Vitals and overall page-experience scores, meaning it can influence organic search visibility. This is a quick, targeted fix with an outsized impact on inclusivity, revenue, and legal risk.

See the complete Error not associated guide for every platform and the full background.