Høyring - Hovudplan for Vatn og Avløp 2023-2033 - Hovedportal

Postliste - Hovedportal

Politisk - Hovedportal

Politiske utval - Hovedportal

Tilgjengelegheit - Hovedportal

Dagny Kristin Rødland - Hovedportal

Joanna Grimstad - Hovedportal

Mi side - Hovedportal

Søknadssenter - Hovedportal

Organisasjon - Hovedportal

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

January 2025

December 2024

Giske

Title / URL	Issues
Høyring - Hovudplan for Vatn og Avløp 2023-2033 - Hovedportalwww.giske.kommune.no/kunngjeringar/	5
Postliste - Hovedportalwww.giske.kommune.no/innsyn/postliste/	5
Politisk - Hovedportalwww.giske.kommune.no/tenester/politisk/	5
Politiske utval - Hovedportalwww.giske.kommune.no/innsyn/politiske-utval/	5
Tilgjengelegheit - Hovedportalwww.giske.kommune.no/tilgjengelegheit/	5
Dagny Kristin Rødland - Hovedportalwww.giske.kommune.no/booking/kart-og-eigedom/	5
Joanna Grimstad - Hovedportalwww.giske.kommune.no/booking/flyktning/	5
Mi side - Hovedportalwww.giske.kommune.no/tenester/mi-side/	5
Søknadssenter - Hovedportalwww.giske.kommune.no/soknadssenter/	5
Organisasjon - Hovedportalwww.giske.kommune.no/tenester/organisasjon/	5

Identify the purpose of fields programmatically

Giske

Where this issue has occurred