Corporation Road Bridge update | NELC

Pay it | NELC

Cookie Policy | NELC

October 2025 | Page 3 of 9 | NELC

December 2025 | Page 3 of 3 | NELC

Markets Archives | NELC

Planning and development Archives | NELC

Keeping our area clean, green, and safe | NELC

Streets, travel and parking | NELC

September 2025 | Page 2 of 7 | NELC

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

February 2026

January 2026

North East Lincolnshire Council

	Title / URL	Issues
	Corporation Road Bridge update \| NELCwww.nelincs.gov.uk/corporation-road-bridge-update-3/	5
	Pay it \| NELCwww.nelincs.gov.uk/pay-it/	5
	Cookie Policy \| NELCwww.nelincs.gov.uk/cookie-policy/	5
	October 2025 \| Page 3 of 9 \| NELCwww.nelincs.gov.uk/2025/10/page/3/	5
	December 2025 \| Page 3 of 3 \| NELCwww.nelincs.gov.uk/2025/12/page/3/	5
	Markets Archives \| NELCwww.nelincs.gov.uk/category/markets/	5
	Planning and development Archives \| NELCwww.nelincs.gov.uk/category/planning-and-development/	5
	Keeping our area clean, green, and safe \| NELCwww.nelincs.gov.uk/keeping-our-area-clean-and-safe/	5
	Streets, travel and parking \| NELCwww.nelincs.gov.uk/streets-travel-and-parking/	5
	September 2025 \| Page 2 of 7 \| NELCwww.nelincs.gov.uk/2025/09/page/2/	5

Identify the purpose of fields programmatically

North East Lincolnshire Council

Where this issue has occurred