KMPT | Contact us

KMPT | Join our Research Community

KMPT | Compliments and complaints

KMPT | Board meetings

KMPT | KMPT Freedom of Information

KMPT | KMPT Friends for Mental Health

KMPT | Contact and register

KMPT | Speak to Sheila

KMPT | Return to Practice

KMPT | KMPT newsletters

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

January 2026

December 2025

Kent and Medway NHS and Social Care Partnership Trust

Title / URL	Issues
KMPT \| Contact uswww.kmpt.nhs.uk/contact-us/	32
KMPT \| Join our Research Communitywww.kmpt.nhs.uk/get-involved/research/join-our-research-community/	7
KMPT \| Compliments and complaintswww.kmpt.nhs.uk/get-involved/feedback/compliments-and-complaints/	4
KMPT \| Board meetingswww.kmpt.nhs.uk/about-us/trust-board/board-meetings/	3
KMPT \| KMPT Freedom of Informationwww.kmpt.nhs.uk/about-us/freedom-of-information/	3
KMPT \| KMPT Friends for Mental Healthwww.kmpt.nhs.uk/get-involved/friends-of-mental-health/	2
KMPT \| Contact and registerwww.kmpt.nhs.uk/get-involved/volunteering/contact-and-register/	2
KMPT \| Speak to Sheilawww.kmpt.nhs.uk/get-involved/feedback/speak-to-sheila/	2
KMPT \| Return to Practicewww.kmpt.nhs.uk/work-with-us/return-to-practice/	2
KMPT \| KMPT newsletterswww.kmpt.nhs.uk/news-and-events/kmpt-newsletters/	1

Identify the purpose of fields programmatically

Kent and Medway NHS and Social Care Partnership Trust

Where this issue has occurred