Semantics

Labels are typically placed on top or to the left of the form fields:

See the Pen Simple Form by Maria () on CodePen.

Notice how you can include autocomplete='on' on the form element and it will apply to all inputs in your form. You can also set different for each input.

Provide labels to describe the purpose of all form control; linking for and id:

  <label for="name">Name</label>
  <input type="text" name="name" id="name" v-model="name"/>

See the Pen Form Label by Maria () on CodePen.

If you inspect this element in your chrome developer tools and open the Accessibility tab inside the Elements tab, you will see how the input gets its name from the label:

Warning:

Though you might have seen labels wrapping the input fields like this:

<label>
  Name:
  <input type="text" name="name" id="name" v-model="name"/>
</label>

Explicitly setting the labels with an matching id is better supported by assistive technology.

aria-label

You can also give the input an accessible name with aria-label.

<label for="name">Name</label>
<input type="text" name="name" id="name" v-model="name" :aria-label="nameLabel"/>

See the Pen by Maria (@mlama007) on .

aria-labelledby

Using is similar to aria-label expect it is used if the label text is visible on screen. It is paired to other elements by their id and you can link multiple ids:

See the Pen Form ARIA labelledby by Maria () on CodePen.

aria-describedby

aria-describedby is used the same way as aria-labelledby expect provides a description with additional information that the user might need. This can be used to describe the criteria for any input:

<form class="demo" action="/dataCollectionLocation" method="post" autocomplete="on">
  <h1 id="billing">Billing</h1>
  <div class="form-item">
    <input type="text" name="name" id="name" v-model="name" aria-labelledby="billing name" aria-describedby="nameDescription"/>
  </div>
  <button type="submit">Submit</button>
</form>

See the Pen by Maria (@mlama007) on .

You can see the description by instecting Chrome DevTools:

Avoid using placeholders as they can confuse many users.

One of the issues with placeholders is that they don’t meet the color contrast criteria by default; fixing the color contrast makes the placeholder look like pre-populated data in the input fields. Looking at the following example, you can see that the Last Name placeholder which meets the color contrast criteria looks like pre-populated data:

See the Pen by Maria (@mlama007) on .

It is best to provide all the information the user needs to fill out forms outside any inputs.

  <fieldset>
    <legend>Using aria-labelledby</legend>
    <label id="date-label" for="date">Current Date:</label>
    <input type="date" name="date" id="date" aria-labelledby="date-label date-instructions" />
    <p id="date-instructions">MM/DD/YYYY</p>
  </fieldset>

Alternatively, you can attach the instructions to the input with aria-describedby:

  <fieldset>
    <legend>Using aria-describedby</legend>
    <label id="dob" for="dob">Date of Birth:</label>
    <input type="date" name="dob" id="dob" aria-describedby="dob-instructions" />
    <p id="dob-instructions">MM/DD/YYYY</p>
  </fieldset>

See the Pen by Maria (@mlama007) on .

Usually it is not recommended to visually hide labels, even if the input has an accessible name. However, if the functionality of the input can be understood with surrounding content, then we can hide the visual label.

Let’s look at this search field:

We can do this because the search button will help visual users identify the purpose of the input field.

We can use CSS to visually hide elements but keep them available for assistive technology:

.hidden-visually {
  position: absolute;
  overflow: hidden;
  white-space: nowrap;
  margin: 0;
  height: 1px;
  width: 1px;
  clip: rect(0 0 0 0);
}

See the Pen Form Search by Maria () on CodePen.

aria-hidden=”true”

Adding aria-hidden="true" will hide the element from assistive technology but leave it visually available for other users. Do not use it on focusable elements, purely on decorative, duplicated or offscreen content.

<p>This is not hidden from screen readers.</p>
<p aria-hidden="true">This is hidden from screen readers.</p>

When using buttons inside a form, you must set the type to prevent submitting the form. You can also use an input to create buttons:

<form action="/dataCollectionLocation" method="post" autocomplete='on'>
  <!-- Buttons -->
  <button type="button">Cancel</button>
  <button type="submit">Submit</button>
  <!-- Input buttons -->
  <input type="button" value="Cancel">
  <input type="submit" value="Submit">
</form>

See the Pen Form Buttons by Maria () on CodePen.

Functional Images

You can use this technique to create functional images.

• Input fields

  • These images will act as a submit type button on forms

<form role="search">
  <label for="searchIcon" class="hidden-visually">Search: </label>
  <input type="text" name="searchIcon" id="searchIcon" v-model="searchIcon">
  <button type="submit">
    <i class="fas fa-search" aria-hidden="true"></i>
    <span class="hidden-visually">Search</span>
</form>

See the Pen Functional Images by Maria () on CodePen.