Have you ever started typing into a form and had your browser suggest a saved value? HTML can help the browser decide which value belongs in which field. The autocomplete token username is used for account sign-in name.
What username tells the browser
Account sign-in name.
This is a hint, not an instruction to fill a value automatically. Browsers and password managers consider settings, saved data, permissions and other signals before offering suggestions.
Example form field
<form action="/example" method="post">
<label for="detail-field">Username</label>
<input id="detail-field" name="detail" type="text" autocomplete="username">
<button type="submit">Continue</button>
</form>Understanding the example
The autocomplete="username" attribute labels this field for autofill. Its visible <label> still tells people what to type, and its name attribute determines the key sent when a form is submitted.
Autocomplete helps password managers locate the account identifier.
A correct token improves convenience but does not prove that the value is accurate. Keep accessible labels and appropriate server-side validation.
Try it yourself
Save the example as an HTML file, and test the field with browser autofill enabled. Inspect the autocomplete value and compare it with the field label. Browser behavior depends on available saved information, so a missing suggestion is not necessarily an HTML mistake.
Common Beginner Mistakes
- Autocomplete helps password managers locate the account identifier.
- Leaving out the visible label because the browser might autofill the field.
- Treating autofill suggestions as verified or safe data.
Key Takeaways
usernamedescribes account sign-in name.- Autocomplete helps password managers locate the account identifier.
- Autocomplete helps users; it does not replace labeling, accessibility or validation.