Issue Summary

The purpose of "Email confirmation to", "First Name", and so on input fields is not identified programmatically, as the “autocomplete” attribute is not provided.

Test URLs

mycolorado-general-support

mycolorado-accessibility-support

Steps to Reproduce

1. Open the myColorado support request form on Android and iOS  devices.
2. Use a screen reader (VoiceOver on iOS or TalkBack on Android) to navigate the form fields.
3. Note that no suggestions appear and the screen reader does not announce saved input.
4. Inspect the code of the specified input fields.
5. Observe that the input fields do not have “autocomplete” attribute.

Screen Recording

Input-field-noautocompleteattribute.mp4

Actual Results

The purpose of "Email confirmation to", "First Name", "Last Name", "Email Address", and "Phone Number" input fields is not identified programmatically. If the purpose of the input fields is not defined programmatically, information can not be customized.

Users with learning and mobility impairments will not be able to access the information in different modalities provided by user agents, such as browsers and assistive technologies.

Expected Results

The purpose of the input fields collecting information about the user, should be defined programmatically using 'autocomplete' attribute. This will make it easier for users with learning and mobility impairments to fill up the form.

Use the HTML 5.2 autocomplete attribute to add token values for "Email confirmation to", "Email address", "First Name", "Last Name", and "Phone Number" fields. This improves the browser's autofill and helps plug-ins fill details for users with mobility and cognitive impairments.

For more information, refer ->

https://www.w3.org/WAI/WCAG21/Techniques/html/H98

https://www.w3schools.com/tags/att_input_autocomplete.asp

Code Snippet

<input id="email" aria-describedby="email-field-description field-error" aria-labelledby="email-label" type="text" name="email" autocomplete="email" ...>

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.

Environment

iPhone 15 Pro Max
iOS Version 26.0
Android Version 14
Chrome - Version 140.0.7339.207
Safari - Version 26
TalkBack
Voiceover - Version Latest