Reporting a safeguarding concern | Your Place

Making a complaint | Your Place

Reporting a maintenance issue | Your Place

Resident stories – Richard | Your Place

News stories and blog | Your Place

Resident volunteering | Your Place

Fundraise at home | Your Place

Good Work Standard Employer | Your Place

Resident stories – Amar | Your Place

Stephen Timms MP Visits | Your Place

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 2025

December 2024

Your Place

Title / URL	Issues
Reporting a safeguarding concern \| Your Placeyour-place.org.uk/reporting-a-safeguarding-concern/	9
Making a complaint \| Your Placeyour-place.org.uk/making-a-complaint/	9
Reporting a maintenance issue \| Your Placeyour-place.org.uk/reporting-a-maintenance-issue/	9
Resident stories – Richard \| Your Placeyour-place.org.uk/resident-stories-richard/	7
News stories and blog \| Your Placeyour-place.org.uk/news-stories-and-blog/	7
Resident volunteering \| Your Placeyour-place.org.uk/resident-volunteering/	7
Fundraise at home \| Your Placeyour-place.org.uk/fundraise-at-home/	7
Good Work Standard Employer \| Your Placeyour-place.org.uk/good-work-standard-employer/	7
Resident stories – Amar \| Your Placeyour-place.org.uk/resident-stories-amar/	7
Stephen Timms MP Visits \| Your Placeyour-place.org.uk/stephen-timms-visits/	7

Identify the purpose of fields programmatically

Your Place

Where this issue has occurred