How to fix error not associated on Webflow

Steps for Webflow

1. Open your Webflow project in the Designer.
2. Select the Form Block containing the field with validation errors, then click on the individual input element.
3. In the Element Settings panel (right sidebar), scroll to 'Custom Attributes' and add: Name = aria-describedby, Value = FIELDNAME-error (matching the id you will give the error element).
4. Add a Text Block element directly after the input inside the same Form Block wrapper; set its ID to FIELDNAME-error and set its initial visibility to hidden (toggle display:none via class).
5. In the Webflow Interactions panel (or in a custom <script> added via Project Settings → Custom Code → Footer Code), write JavaScript that on form submission detects invalid fields and: sets aria-invalid='true' on the input, reveals the error Text Block, and populates its text content.
6. Publish the site and test with VoiceOver (Mac) or NVDA (Windows).

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.