LNG Gas Processing Software and Solutions | AVEVA

AVEVA Partner Ecosystem

Software Solutions For Manufacturing | AVEVA

Engineering Software Solutions | AVEVA

Chemical Industry Software Solutions | AVEVA

Oil & Gas Software Solutions | Oil & Gas Industry | AVEVA

Marine Engineering Software & Solutions | AVEVA

What is Operations software? | Operations solutions | AVEVA

Industrial Software Solutions | AVEVA

Engineering, procurement, construction (EPC)

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

Aveva

	Title / URL	Issues
	LNG Gas Processing Software and Solutions \| AVEVAwww.aveva.com/en/industries/oil-gas/lng/	12
	AVEVA Partner Ecosystemwww.aveva.com/en/about/partners/	3
	Software Solutions For Manufacturing \| AVEVAwww.aveva.com/en/industries/manufacturing/	2
	Engineering Software Solutions \| AVEVAwww.aveva.com/en/solutions/engineering/	2
	Chemical Industry Software Solutions \| AVEVAwww.aveva.com/en/industries/chemicals/	2
	Oil & Gas Software Solutions \| Oil & Gas Industry \| AVEVAwww.aveva.com/en/industries/oil-gas/	2
	Marine Engineering Software & Solutions \| AVEVAwww.aveva.com/en/industries/marine/	2
	What is Operations software? \| Operations solutions \| AVEVAwww.aveva.com/en/solutions/operations/	2
	Industrial Software Solutions \| AVEVAwww.aveva.com/en/solutions/	2
	Engineering, procurement, construction (EPC)www.aveva.com/en/industries/epc/	2

Identify the purpose of fields programmatically

Aveva

Where this issue has occurred