Our Approach – Safer Places

J9 Initiative – Safer Places

News – Safer Places

First time visit: View without clicking anything

Partners – Safer Places

Donate – Safer Places

Events – Safer Places

Not Found – Safer Places

Browse Safely – Safer Places

Accessibility – Safer Places

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

Safer Places

Title / URL	Issues
Our Approach – Safer Placeswww.saferplaces.co.uk/our-approach	5
J9 Initiative – Safer Placeswww.saferplaces.co.uk/j9-initiative	5
News – Safer Placeswww.saferplaces.co.uk/news	5
First time visit: View without clicking anythingwww.saferplaces.co.uk/	5
Partners – Safer Placeswww.saferplaces.co.uk/partners	5
Donate – Safer Placeswww.saferplaces.co.uk/donate?amount=25	5
Events – Safer Placeswww.saferplaces.co.uk/pages/events	5
Not Found – Safer Placeswww.saferplaces.co.uk/invented-url-for-404-page	5
Browse Safely – Safer Placeswww.saferplaces.co.uk/browse-safely	5
Accessibility – Safer Placeswww.saferplaces.co.uk/accessibility	5

Identify the purpose of fields programmatically

Safer Places

Where this issue has occurred