Placeholder text is not a label. It disappears the moment a user starts typing, and many assistive technologies don't reliably announce it in the first place. A real <label> costs one line and fixes the majority of form accessibility complaints we see.

<label for="email">Email address</label>
<input id="email" type="email" name="email" required>

Group related fields

<fieldset>
  <legend>Shipping address</legend>
  ...
</fieldset>

Errors need to be announced, not just shown

A red border alone communicates nothing to a screen reader. Pairing it with aria-invalid="true" and a text message linked via aria-describedby means the error is actually heard, not just seen.

Label every field, even the "obvious" ones

A placeholder is not a label - it disappears the moment someone starts typing, so anyone who loses their place (which includes plenty of sighted users, not only screen reader users) loses the field's purpose along with it. Every input needs a <label> tied to it with a matching for/id pair, full stop, even for something as "obvious" as a single search box.

<label for="search">Search the site</label>
<input id="search" name="search" type="search">

Error messages need to be heard, not just seen

A red border on an invalid field communicates nothing to someone who can't see color, and a screen reader won't announce it unless the error text is programmatically tied to the field or placed in a live region. Pairing aria-describedby with a visible, specific error message - "Enter a valid email address" rather than a generic "Invalid input" - fixes the problem for every user at once, sighted or not.