City Demographics | Seaside, CA

Weather | Seaside, CA

How Do I... | Seaside, CA

About Seaside | Seaside, CA

Quick Links • Helpful Links

Residents | Seaside, CA

Pages • Seaside, CA • CivicEngage

Custom404 • Seaside, CA • CivicEngage

Strategic Plan | Seaside, CA

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

City of Seaside

	Title / URL	Issues
	City Demographics \| Seaside, CAwww.ci.seaside.ca.us/283/City-Demographics	5
	Weather \| Seaside, CAwww.ci.seaside.ca.us/415/Weather	5
	How Do I... \| Seaside, CAwww.ci.seaside.ca.us/9/How-Do-I	5
	About Seaside \| Seaside, CAwww.ci.seaside.ca.us/375/About-Seaside	5
	Quick Links • Helpful Linkswww.ci.seaside.ca.us/QuickLinks.aspx?CID=11	5
	Residents \| Seaside, CAwww.ci.seaside.ca.us/101/Residents	5
	Pages • Seaside, CA • CivicEngagewww.ci.seaside.ca.us/Accessibility	5
	Custom404 • Seaside, CA • CivicEngagewww.ci.seaside.ca.us/invented-url-for-404-page	5
	Pages • Seaside, CA • CivicEngagewww.ci.seaside.ca.us/copyright	5
	Strategic Plan \| Seaside, CAwww.ci.seaside.ca.us/609/Strategic-Plan	5

Identify the purpose of fields programmatically

City of Seaside

Where this issue has occurred