...
Forms Checklist and Overview
Ensure that information, structure, and relationships can be programmatically determined or are available in textNotify users when form elements are required to complete.
Create a logical structure and tab order within forms.
Ensure that form related instructions do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.
Ensure that the purpose of a form input collecting information about the user can be programmatically determined, so that user agents can extract and present that information to the user without having them type in the info (autocomplete).
Ensure that form related alert and error messaging do not only rely on color to convey the information.
Ensure that keyboard only users and screen reader users who rely on using a keyboard are able to navigate, complete and submit forms.
Ensure that content does not "trap" keyboard focus within subsections of content on a Web page. For example when navigating to and away from a calendar widget/component.
Provide users with adequate time to complete and submit forms.
Provide sighted keyboard only users with a keyboard focus indicator to let them know which form element has keyboard focus. The keyboard focus indicator needs to provide adequate color contrast between foreground and background.
Ensure that entering data or selecting a form control has predictable effects.
Ensure that form components that have the same functionality within a set of web pages are identified consistently.
Provide users with a mechanism to initiate a change in form behavior and form submissions.
Make users aware of important changes in content that are not given focus, such as inline error messages.
Provide role, state and value information in connection with form elements in order to make functionality accessible to assistive technology.
...