Our services | Princess Alexandra Hospital

Search | Princess Alexandra Hospital

News and events | Princess Alexandra Hospital

Our teams | Princess Alexandra Hospital

Transparency reports 2018-2019 | Princess Alexandra Hospital

Flexible workers | Princess Alexandra Hospital

Transparency reports 2016-2017 | Princess Alexandra Hospital

Clinical services | Princess Alexandra Hospital

To comply with WCAG 2.1, fields must identify what their purpose is _programmatically_. If done correctly,
this allows browsers to help users fill in forms with known information, such as their name and email address.

This is accomplished via the `autocomplete` attribute, which should be set to a 
[supported value](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete) wherever
appropriate, e.g. 

```html
<label for="name">
  First Name
</label>
<input id="name" type="text" autocomplete="given-name">
```

For fields where `autocomplete` is not appropriate, e.g. due to security, or the field not matching the
specification, the specific field should be ignored.

## Methodology

* All fields which could support `autocomplete` (e.g. text fields)
  are checked. Other fields - like dropdown menus - are ignored.
* The [accessible name](https://www.w3.org/TR/accname-1.2/) of each field is considered. In most cases this
  will be the `<label>` for the field.
* If the name matches a known pattern the field 
  must have an appropriate `autocomplete` value specified.
  For example, an `<input>` with type `text` with a label of 
  "First Name" would be expected to have an autocomplete value 
  of `given-name` or similar.

Note that using `autocomplete="on"` is not sufficient to pass this check, a
specific named autocomplete value must be used. See the
[supported values](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete).

## Troubleshooting

If a field is a false positive, check whether the field has an 
appropriate accessible name (i.e. a `<label>` or `aria-label`).

If the label is incorrect, Silktide may assume that the field 
requires `autocomplete` where it does not. You should fix the 
label to avoid this.

Otherwise, you can simply ignore the specific field.

## More information

* [How to use HTML 5.2 attributes](https://www.w3.org/WAI/WCAG21/Techniques/html/H98)

identify-input-purpose

June 2024

May 2024

The Princess Alexandra Hospital NHS Trust

Title / URL	Issues
Our services \| Princess Alexandra Hospitalwww.pah.nhs.uk/our-services	5
Search \| Princess Alexandra Hospitalwww.pah.nhs.uk/search	5
News and events \| Princess Alexandra Hospitalwww.pah.nhs.uk/news-and-events	5
Our services \| Princess Alexandra Hospitalwww.pah.nhs.uk/our-services?ser_atoz=K	5
Our teams \| Princess Alexandra Hospitalwww.pah.nhs.uk/our-teams	5
Transparency reports 2018-2019 \| Princess Alexandra Hospitalwww.pah.nhs.uk/transparency-reports-2018-19	5
Flexible workers \| Princess Alexandra Hospitalwww.pah.nhs.uk/flexible-workers	5
Transparency reports 2016-2017 \| Princess Alexandra Hospitalwww.pah.nhs.uk/transparency-reports-2016-17	5
Our services \| Princess Alexandra Hospitalwww.pah.nhs.uk/our-services/service/dietetics-41/	5
Clinical services \| Princess Alexandra Hospitalwww.pah.nhs.uk/clinical-services	5

Identify the purpose of fields programmatically

The Princess Alexandra Hospital NHS Trust

Where this issue has occurred