Helaba - Presse und Newsroom

Helaba - Energie und Versorger

Helaba - Die Landesbank Hessen-Thüringen

Helaba - Für Auszubildende

Helaba - Bund, Länder, Kommunen

Helaba - Ergebnisse

Helaba - Lösungen für ausgewählte Projekte

Helaba - Finanzkalender

Helaba - Kapitalmärkte

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

July 2025

June 2025

Landesbank Hessen-Thüringen (Helaba)

Title / URL	Issues
Helaba - Presse und Newsroomwww.helaba.com/de/presse/	2
Helaba - Energie und Versorgerwww.helaba.com/de/kunden/energie-und-versorger.php	1
Helaba - Die Landesbank Hessen-Thüringenwww.helaba.com/de/	1
Helaba - Für Auszubildendewww.helaba.com/de/karriere/ausbildung-bank.php	1
Helaba - Bund, Länder, Kommunenwww.helaba.com/de/kunden/oeffentliche-hand.php	1
Helaba - Die Landesbank Hessen-Thüringenwww.helaba.com/	1
Helaba - Ergebnissewww.helaba.com/de/nachhaltigkeit/fakten/ergebnisse.php	1
Helaba - Lösungen für ausgewählte Projektewww.helaba.com/de/projekte/	1
Helaba - Finanzkalenderwww.helaba.com/de/presse/finanzkalender.php	1
Helaba - Kapitalmärktewww.helaba.com/de/geschaeftsfelder/kapitalmaerkte.php	1

Identify the purpose of fields programmatically

Landesbank Hessen-Thüringen (Helaba)

Where this issue has occurred