Members Section | SEUPB

About SEUPB | SEUPB

Our Team | SEUPB

Building Peaceful and Thriving Communities | SEUPB

PEACE Programmes Learning Platform | SEUPB

Current funding opportunities | SEUPB

Development of PEACEPLUS | SEUPB

Contact Us | SEUPB

Guidance for Funded Projects | SEUPB

PEACEPLUS | SEUPB

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 2025

January 2025

Special EU Programmes Body

Title / URL	Issues
Members Section \| SEUPBwww.seupb.eu/members-section	2
About SEUPB \| SEUPBwww.seupb.eu/about-seupb	1
Our Team \| SEUPBwww.seupb.eu/about-seupb/our-team	1
Building Peaceful and Thriving Communities \| SEUPBwww.seupb.eu/peaceplus/overview/themes-and-investment-areas/theme-1	1
PEACE Programmes Learning Platform \| SEUPBwww.seupb.eu/past-programmes/peace-platform	1
Current funding opportunities \| SEUPBwww.seupb.eu/peaceplus/current-funding-opportunities	1
Development of PEACEPLUS \| SEUPBwww.seupb.eu/peaceplus/overview/development-programme	1
Contact Us \| SEUPBwww.seupb.eu/contact-us	1
Guidance for Funded Projects \| SEUPBwww.seupb.eu/peaceplus/guidance-funded-projects	1
PEACEPLUS \| SEUPBwww.seupb.eu/peaceplus	1

Identify the purpose of fields programmatically

Special EU Programmes Body

Where this issue has occurred