Resident Application | HYELM

Data Protection | HYELM

About Us | HYELM

First time visit: View without clicking anything

An Update On Our Old Street Refurbishment. | HYELM

Exciting Housing Opportunity for Key Workers | HYELM

Downloads | HYELM

Privacy Notice | HYELM

Resident Privacy Notice | HYELM

Terms and Conditions | HYELM

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

Hyelm

Title / URL	Issues
Resident Application \| HYELMhyelm.com/resident-application/	6
Data Protection \| HYELMhyelm.com/data-protection/	1
About Us \| HYELMhyelm.com/about-us/	1
First time visit: View without clicking anythinghyelm.com/	1
An Update On Our Old Street Refurbishment. \| HYELMhyelm.com/news/an-update-on-our-old-street-refurbishment/	1
Exciting Housing Opportunity for Key Workers \| HYELMhyelm.com/news/exciting-housing-opportunity-for-key-workers/	1
Downloads \| HYELMhyelm.com/downloads/	1
Privacy Notice \| HYELMhyelm.com/privacy-notice/	1
Resident Privacy Notice \| HYELMhyelm.com/resident-privacy-notice/	1
Terms and Conditions \| HYELMhyelm.com/terms-and-conditions/	1

Identify the purpose of fields programmatically

Hyelm

Where this issue has occurred