Required: All form elements are able to be utilized fully via keyboard.
Required: Input fields are associated with labels via “for-id” syntax (
title attribute used alternatively, when necessary/by visual requirement) and buttons or button inputs are properly labeled (via encapsulated text or
value attribute, respectively).
Required: If a traditional visual challenge CAPTCHA is used (not advised), an audio challenge alternative is provided and/or a method requiring only text-to-speech output is provided.
Strongly Recommended: Fieldsets with short descriptive legends group associated radio buttons or check boxes.
Strongly Recommended: Order of form elements flows logically and associated elements are proximate and in a logical order.
Strongly Recommended: Form errors are indicated by focusing the errors list on page submit or by focusing first error field and ensuring error message is accessible to a screen reader user by using
aria-labelledby or other associative labeling method
Strongly Recommended: Form required fields are identified textually (via alt on an image of an asterisk, for example) and/or through both
Strongly Recommended: Help prompts in forms are accessible to a screen reader and properly associated with the relevant field, using
aria-labelledby or other associative labeling method.
Strongly Recommended: Dynamic, scripted elements within a form (contextual reveals, etc.) do not disrupt form fill out and are tested to be screen reader accessible.
Recommended: Users are able to confirm and edit long/multi-page form changes before submitting.
Recommended: Form submission errors are indicated with text proximate to the field and associated with aria-labelledby or other associative labeling method
Recommended: Forms do not use links for buttons.