Register

Contact

Tide tables

Tomorrow's shipping movements

Safety and regulations

Today

Using the port for recreation

KHM Portsmouth

Shipping movements and planned diving

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

Royal Navy

	Title / URL	Issues
	Registerwww.royalnavy.mod.uk/careers/register-for-newsletter	3
	Contactwww.royalnavy.mod.uk/khm/plymouth/contact	2
	Contactwww.royalnavy.mod.uk/khm/clyde/contact	2
	Tide tableswww.royalnavy.mod.uk/khm/clyde/port-information/tide-tables	1
	Tomorrow's shipping movementswww.royalnavy.mod.uk/khm/portsmouth/shipping-movements/tomorrow	1
	Safety and regulationswww.royalnavy.mod.uk/khm/plymouth/safety-and-regulations	1
	Todaywww.royalnavy.mod.uk/khm/plymouth/shipping-movements/today	1
	Using the port for recreationwww.royalnavy.mod.uk/khm/plymouth/using-the-port-for-recreation	1
	KHM Portsmouthwww.royalnavy.mod.uk/khm/portsmouth	1
	Shipping movements and planned divingwww.royalnavy.mod.uk/khm/plymouth/shipping-movements	1

Identify the purpose of fields programmatically

Royal Navy

Where this issue has occurred