MRM | IPG

BPN | IPG

Craft | IPG

Acxiom | IPG

Contact Us | IPG

People using screen readers are not able to see the layout of a form. To make forms
accessible, they must define explicit text labels for each form control. 

Usually the best solution is to use a `<label>` element. The label may be linked to 
by the form control:

```html
<label for="name">Full name</label>
<input type="name" id="name">
```

or the `<label>` can be wrapped around the form control:

```html
<label>
    Full name <input type="name">
</label>
```

Buttons are different, as their labels are specified by the code for the button, e.g.

```html
<input type="submit" value="Send message">
<button>Send message</button>
```

Alternatively ARIA attributes, such as `aria-label` may be used, but this information
will not be conveyed to visual users. For more information, see [W3C's guide to labeling controls](https://www.w3.org/WAI/tutorials/forms/labels/).

Hidden input fields (`<input type="hidden">`) do not require labels.
Note that the `placeholder` attribute 
[should not be used as an alternative to a label](https://www.w3.org/TR/html/sec-forms.html#the-placeholder-attribute),
nor should the `title` attribute.

## Custom roles

Note that this check considers the underlying accessible role of an element, which can be 
different from the tag itself.

For example, this `<div>` has a `role` of `button`, and so is expected to have a label, like
a button would.

```html
<div role="button"></div>
```

Title / URL	Issues
MRM \| IPGwww.interpublic.com/our-companies/mrm/	34
BPN \| IPGwww.interpublic.com/our-companies/bpn/	26
Craft \| IPGwww.interpublic.com/our-companies/craft/	23
Acxiom \| IPGwww.interpublic.com/our-companies/acxiom/	9
Contact Us \| IPGwww.interpublic.com/contact-us/	3

Ensure form controls have labels

Interpublic Group

Where this issue has occurred