Who we are

About us

Annual reports

Our structure

Brief history of the KBC Group

Other KBC sites

Page not found (404)

KBC Economics

Photos

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

December 2025

November 2025

KBC Group NV

	Title / URL	Issues
	Who we arewww.kbc.com/en/about-us/who-we-are.html?zone=topnav	1
	ENwww.kbc.com/en.html?zone=topnav	1
	About uswww.kbc.com/en/about-us.html?zone=topnav	1
	Annual reportswww.kbc.com/en/investor-relations/reports/annual-reports.html?zone=topnav	1
	Our structurewww.kbc.com/en/about-us/our-structure.html?zone=topnav	1
	Brief history of the KBC Groupwww.kbc.com/en/about-us/our-history/brief-history-of-the-kbc-group.html?zone=topnav	1
	Other KBC siteswww.kbc.com/en/no-menu/andere-sites.html?zone=topnav	1
	Page not found (404)www.kbc.com/invented-url-for-404-page.html	1
	KBC Economicswww.kbc.com/en/newsroom/kbc-economics.html?zone=topnav	1
	Photoswww.kbc.com/en/newsroom/media-gallery/photos.html?zone=topnav	1

Identify the purpose of fields programmatically

KBC Group NV

Where this issue has occurred