Grand Union Canal | Walks near me

Lee Navigation | London Canal Map

First time visit: View without clicking anything

Providing places for people | Canal & River Trust

Cymru | Canal & River Trust

Threats to our waterways | Canal & River Trust

Events | Canal & River Trust

Keeping history alive | Canal & River Trust

Lancaster Canal | Canal network map

Regent's Canal | London Canals

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 2025

May 2025

Canal & River Trust

	Title / URL	Issues
	Grand Union Canal \| Walks near mecanalrivertrust.org.uk/canals-and-rivers/grand-union-canal	1
	Lee Navigation \| London Canal Mapcanalrivertrust.org.uk/canals-and-rivers/lee-navigation	1
	First time visit: View without clicking anythingcanalrivertrust.org.uk/	1
	Providing places for people \| Canal & River Trustcanalrivertrust.org.uk/our-cause/providing-places-for-people	1
	Cymru \| Canal & River Trustcanalrivertrust.org.uk/cy/cymru	1
	Threats to our waterways \| Canal & River Trustcanalrivertrust.org.uk/our-cause/threats-to-our-waterways	1
	Events \| Canal & River Trustcanalrivertrust.org.uk/things-to-do/events	1
	Keeping history alive \| Canal & River Trustcanalrivertrust.org.uk/our-cause/keeping-history-alive	1
	Lancaster Canal \| Canal network mapcanalrivertrust.org.uk/canals-and-rivers/lancaster-canal	1
	Regent's Canal \| London Canalscanalrivertrust.org.uk/canals-and-rivers/regents-canal	1

Identify the purpose of fields programmatically

Canal & River Trust

Where this issue has occurred