How to fix label on Squarespace

Steps for Squarespace

1. For Squarespace Form Blocks: click Edit on the form block, then click the pencil icon on each field. In the field settings, ensure 'Label' is filled in — Squarespace renders this as a `<label>` tag.
2. If you want to hide labels visually while keeping them accessible, go to Design → Custom CSS and add: `.field-label { position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0,0,0,0); white-space: nowrap; }` — this hides labels visually but keeps them in the DOM for screen readers.
3. For the Search Block (header/footer), Squarespace automatically provides an `aria-label` on the input; if a custom header overrides this, add the fix via Settings → Advanced → Code Injection (header code) to inject a small script that sets `aria-label` on the element.
4. For Newsletter Blocks, open the block editor, ensure the Email field has a label entered in the form settings.
5. Save and verify with the axe browser extension.

What is label?

Every form field on your site — search boxes, email sign-up fields, checkout inputs, contact forms — must have a label that describes what the field is for. A "label" in web terms is either a visible `<label>` element paired with the input, or a special accessibility attribute (like `aria-label`) that provides the same description invisibly. When a form field has no label at all, the browser and assistive technology have nothing to announce to the user about what that field is asking for. WCAG Success Criterion 4.1.2 requires all form controls to have a name that assistive technology can read out loud.

Screen-reader users — including customers with visual impairments — will hear something like "edit text, blank" when they reach an unlabelled field, with no clue what to type. This makes checkout, sign-up, and contact forms completely unusable for those customers, directly costing you sales and leads. From a legal standpoint, unlabelled form fields are one of the most frequently cited accessibility violations in ADA and WCAG-based lawsuits and demand letters targeting e-commerce stores. Google also uses accessible markup signals as a quality indicator, so fixing labelling issues supports your site's overall technical health. Fixing this is typically a quick code change that immediately improves usability for everyone, including mobile users who rely on tap-targets and auto-fill.

See the complete Label guide for every platform and the full background.