Loading...
Loading content...
Loading content...
Use HTML autocomplete attributes on form fields collecting user data.
Why it matters: Allows browsers and assistive tools to auto-fill forms, helping users with memory or motor impairments.
The purpose of each input field collecting information about the user can be programmatically determined when: (Level AA) The input field serves a purpose identified in the Input Purposes for User Interface Components section; and the content is implemented using technologies with support for identifying the expected meaning for form input data.
What This Means: This success criterion requires that form fields collecting information about users must have their purpose programmatically identified using HTML autocomplete attributes. This allows browsers and assistive technologies to understand what type of information each field expects, enabling auto-fill functionality and better user experience.
Why It's Important: Users with cognitive disabilities may have difficulty remembering information like addresses, phone numbers, or names. Users with motor disabilities may find typing difficult. By identifying input purposes, browsers can auto-fill forms using saved information, significantly reducing the cognitive and physical effort required. This also helps prevent input errors and speeds up form completion.
Add appropriate autocomplete attributes to all form fields that collect user information. Use standard HTML autocomplete values like 'name', 'email', 'tel', 'address-line1', 'postal-code', 'country', etc. For password fields, use 'current-password' for login forms and 'new-password' for registration/change password forms. The autocomplete attribute should match the actual purpose of the field.
This criterion ensures that users with cognitive disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
This criterion ensures that users with motor disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
Impact: When this criterion is properly implemented, it removes barriers for these user groups and creates a more inclusive web experience for everyone.
Form fields have no autocomplete attributes, requiring manual entry every time.
<input type="text" name="name"><input type="email" name="email">Form fields use autocomplete attributes, enabling browser auto-fill.
<input type="text" name="name" autocomplete="name"><input type="email" name="email" autocomplete="email">This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 1.3.5 Identify Input Purpose are met. Check off items as you complete them.
To meet this success criterion, ensure the following requirements are met:
While meeting the minimum requirements ensures compliance, consider these enhancements for a better user experience:
Autocomplete is just for convenience, not accessibility.
Autocomplete is crucial for users with cognitive or motor disabilities who may have difficulty typing or remembering information. It's a Level AA requirement.
I can use any autocomplete value I want.
Autocomplete values must use standard HTML values. Browsers and assistive technologies recognize these standard values to provide auto-fill functionality.
Form fields without autocomplete attributes.
Add appropriate autocomplete attributes to all fields collecting user information. Use standard values like 'name', 'email', 'tel', 'address-line1', etc.
Using incorrect or non-standard autocomplete values.
Use standard HTML autocomplete values. Refer to the HTML specification for the complete list of valid values.
Not using autocomplete on password fields.
Use autocomplete='current-password' for login forms and 'new-password' for registration/change password forms.
Note: These are official W3C resources for 1.3.5. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 1.3.5 Identify Input Purpose correctly requires understanding your specific context. Code solutions vary significantly based on multiple factors:
HTML, React, Vue, Angular, PHP, Python, and other frameworks each have different patterns and best practices.
Server-side rendering, client-side rendering, static generation, and hybrid approaches require different solutions.
Your existing components, styling approach, and UI library influence how accessibility must be implemented.
Your specific user base, content type, and interaction patterns determine the most appropriate implementation.
We provide tailored implementation guidance by analyzing your specific technology stack, coding patterns, design system, and project requirements. Our team reviews your codebase and provides custom solutions that integrate seamlessly with your existing architecture.
Get Custom Implementation HelpPart of
Perceivable PrincipleGuideline
1.3 Adaptable