Your newsletter - RWP

Get in touch - RWP

Happy in my Home - RWP

Alan Greig Blog - RWP

Real stories - RWP

About us - RWP

Annear Place Update - RWP

Accessibility statement - RWP

Living in your home - RWP

First time visit: View without clicking anything

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

March 2025

February 2025

Reside with Progress

Title / URL	Issues
Your newsletter - RWPwww.residewithprogress.org.uk/living-in-your-home/your-newsletter/	4
Get in touch - RWPwww.residewithprogress.org.uk/get-in-touch/	4
Happy in my Home - RWPwww.residewithprogress.org.uk/news/happy-in-my-home/	1
Alan Greig Blog - RWPwww.residewithprogress.org.uk/news/alan-greig-blog/	1
Real stories - RWPwww.residewithprogress.org.uk/real-stories/	1
About us - RWPwww.residewithprogress.org.uk/about-us/	1
Annear Place Update - RWPwww.residewithprogress.org.uk/news/annear-place-update/	1
Accessibility statement - RWPwww.residewithprogress.org.uk/accessibility-statement/	1
Living in your home - RWPwww.residewithprogress.org.uk/living-in-your-home/	1
First time visit: View without clicking anythingwww.residewithprogress.org.uk/	1

Identify the purpose of fields programmatically

Reside with Progress

Where this issue has occurred