Form Input, Labels, and Instructions

Accessibility Techniques for Form Inputs, Labels, and Instructions
Topic	Technique	WCAG AA Requirement
Labels for Inputs	Programmatic Labels: Labels MUST be programmatically associated with their corresponding elements. Testing methodology 1.3.1.c	Required WCAG 1.3.1
	Discernible Label Text: Labels MUST be available as programmatically discernible text. Testing methodology 1.3.1.c	Required WCAG 1.3.1
	Meaningful Labels: Labels MUST be meaningful. Testing methodology 1.3.1.c	Required WCAG 1.3.1
	Sensory Dependencies of Labels: Labels MUST NOT rely solely on references to sensory characteristics. Testing methodology 1.3.3.a Testing methodology 1.3.3.b	Required WCAG 1.3.3
	Icons as Labels: Icons/graphics MAY be used as the only visual label (without visual text) only if the meaning of the icon is visually self-evident AND if there is a programmatically associated semantic label available to assistive technologies. Testing methodology 1.3.1.c	Required WCAG 1.3.1
	Placeholder Text: Placeholder text is allowed, but MUST NOT be used as the only method of providing a label for a text input. Testing methodology 1.3.1.c	Required WCAG 1.3.1
	Visible Labels: Labels MUST be visible. Testing methodology 3.3.2.a	Required WCAG 3.3.2
	Label in Name: For user interface components with labels that include text or images of text, the name MUST contain the text that is presented visually.	Required WCAG 2.5.3 (WCAG 2.1)
	Matching Programmatic Label and Visual Label: The programmatic label MUST include the same text presented in the visual label, to facilitate voice activation. Testing methodology 2.5.3	Required WCAG 2.5.3 (WCAG 2.1)
	Multiple Labels for One Input: When multiple labels are used for one element, each label MUST be programmatically associated with the corresponding element. Testing methodology 1.3.1.c	Required WCAG 1.3.1
	One Label for Multiple Inputs: When one label is used for multiple elements, the label MUST be programmatically associated with each of the corresponding elements. Testing methodology 1.3.1.c	Required WCAG 1.3.1
	Visually Adjacent Labels: A label SHOULD be visually adjacent to its corresponding element.	Best Practice
	Programmatically Adjacent Labels: A label SHOULD be adjacent in the DOM to its corresponding element.	Best Practice
Labels for Groups of Inputs	Programmatic Group Labels: Group labels MUST be programmatically associated with the group if the individual labels for each element in the group are insufficient on their own (e.g. a group of radio buttons that has a group label plus individual labels for each radio option). Testing methodology 1.3.1.d	Required WCAG 1.3.1
	Programmatically Determinable Text in Group Labels: Group labels MUST be programmatically determinable. Testing methodology 1.3.1.d	Required WCAG 1.3.1
	Meaningful Group Labels: Group labels MUST be meaningful. Testing methodology 1.3.1.d	Required WCAG 1.3.1
	Sensory Dependencies of Group Labels: Group labels MUST NOT rely solely on references to sensory characteristics. Testing methodology 1.3.3.a Testing methodology 1.3.3.b	Required WCAG 1.3.3
	Visible Group Labels: Group labels MUST be visible. Testing methodology 3.3.2.a	Required WCAG 3.3.2
	Matching Programmatic Label and Visual Label: The programmatic label MUST include the same text presented in the visual label, to facilitate voice activation. Testing methodology 2.5.3.a	Required WCAG 2.5.3 (WCAG 2.1)
	Visually Adjacent Group Labels: Group labels SHOULD be visually adjacent to the grouped elements.	Best Practice
	Programmatically Adjacent Group Labels: Group labels SHOULD be adjacent in the DOM to the grouped elements.	Best Practice
Identify Input Purpose	Identify Input Purpose: The purpose for each common input field that collects an individual's personal data MUST be programmatically defined based on the list of 53 Input Purposes for User Interface Components.	Required WCAG 1.3.5 (WCAG 2.1)
Instructions About Inputs	Programmatic Association of Input Instructions: Instructions for an element MUST be programmatically associated with the element. Testing methodology 3.3.2.b	Required WCAG 3.3.2
	Programmatically Determinable Text in Input Instructions: Instructions for an element MUST be available as programmatically determinable text. Testing methodology 3.3.2.b	Required WCAG 3.3.2
	Meaningful Input Instructions: Instructions for an element MUST be meaningful. Testing methodology 3.3.2.b	Required WCAG 3.3.2
	Visible Input Instructions: Instructions for an element MUST be visible. Testing methodology 3.3.2.a	Required WCAG 3.3.2
	Sensory Dependencies of Input Instructions: Instructions for an element MUST NOT rely solely on references to sensory characteristics. Testing methodology 1.3.3.a Testing methodology 1.3.3.b	Required WCAG 1.3.3
	Hidden Input Instructions: If the instructions for an element are not critical, the instructions MAY be hidden until the user requests them.	Best Practice
	Visually Adjacent Input Instructions: Instructions for an element SHOULD be visually adjacent to the element.	Best Practice
	Programmatically Adjacent Input Instructions: Instructions for an element SHOULD be adjacent in the DOM to the element.	Best Practice
Instructions About an Entire Form, a Group, or a Section	Programmatic Association of Group Instructions: Instructions for groups or sections SHOULD be programmatically associated with the group. Testing methodology 3.3.2.b	Required WCAG 3.3.2
	Programmatically Determinable Text in Group Instructions: Instructions for groups or sections MUST be programmatically determinable. Testing methodology 3.3.2.b	Required WCAG 3.3.2
	Meaningful Group Instructions: Instructions for groups or sections MUST be meaningful. Testing methodology 3.3.2.b	Required WCAG 3.3.2
	Visible Group Instructions: Instructions for groups or sections MUST be visible. Testing methodology 3.3.2.a	Required WCAG 3.3.2
	Sensory Dependencies of Group Instructions: Instructions for groups or sections MUST NOT rely solely on references to sensory characteristics. Testing methodology 1.3.3.a Testing methodology 1.3.3.b	Required WCAG 1.3.3
	Hidden Form Instructions: If the instructions are not critical to understand the purpose of a group or section, the instructions MAY be hidden until the user requests them.	Best Practice
	Visually Adjacent Group Instructions: Instructions for groups or sections SHOULD be visually adjacent to the grouped elements.	Best Practice
	Programmatically Adjacent Group Instructions: Instructions for groups or sections SHOULD be adjacent in the DOM to the grouped elements.	Best Practice
Required Fields	Programmatic Designation: Required fields SHOULD be programmatically designated as such. Note: At a minimum, WCAG requires an informative error message about the field after the user submits the form.	Best Practice
Required Fields	Visual Indicator: Required fields SHOULD have a visual indicator that the field is required.	Best Practice
Data Input Restrictions	Information About Data Input Restrictions: If a field allows only restricted input (e.g. a certain date format, only integers, no more than 4 characters, etc.), the restrictions SHOULD be communicated in the label or instructions. Note: At a minimum, WCAG requires an informative error message about the field after the user submits the form.	Best Practice
Disabled Fields	Awareness of disabled fields: If awareness of a disabled field is essential to understanding the content, an alternative way of communicating information about the disabled field MUST be provided (because disabled fields are not in the normal tab order by default, making it difficult for screen reader users to discover them). Testing methodology 1.3.1.c	Required WCAG 1.3.1
Time Limits	Sufficient Time: Users MUST be allowed sufficient time to complete the form, through at least one of the following methods: No time limit The ability to turn off the time limit The ability to extend the time limit The ability to adjust/customize time limit A minimum of 20 hours to complete the form Note: This requirement can be waived if the time limit is essential to the meaning or purpose of the form (e.g. a timed auction). Testing methodology 2.2.1.a	Required WCAG 2.2.1
Entering Redundant Information	Redundant Entry: Information previously entered by or provided to the user that is required to be entered again in the same process MUST be either auto-populated or available for the user to select, with several allowable exceptions. The allowable exceptions when redundant entry may be required are when: re-entering the information is essential, the information is required to ensure the security of the content, or previously entered information is no longer valid.	Required WCAG 3.3.7 (WCAG 2.2)
Authentication	Accessible Authentication (Minimum): A cognitive function test (such as remembering a password or solving a puzzle) MUST NOT be required for any step in an authentication process unless that step provides at least one of the following: Alternative: Another authentication method that does not rely on a cognitive function test. Mechanism: A mechanism is available to assist the user in completing the cognitive function test. Object Recognition: The cognitive function test is to recognize objects. Personal Content: The cognitive function test is to identify non-text content the user provided to the website. Note: "Object recognition" and "Personal content" may be represented by images, video, or audio. Note: Examples of mechanisms that satisfy this criterion include: support for password entry by password managers to reduce memory need, and copy and paste to reduce the cognitive burden of re-typing.	Required WCAG 3.3.8 (WCAG 2.2)
Authentication	Accessible Authentication (Enhanced): A cognitive function test (such as remembering a password or solving a puzzle) SHOULD NOT be required for any step in an authentication process, unless there is an alternative authentication method without a required cognitive test or there is a mechanism to assist the user in completing the cognitive function test.	Best Practice
Dynamic Forms	See the requirements for Dynamic Content (JavaScript, AJAX).	Required multiple
Custom Form Inputs (JavaScript/ARIA)	See the requirements for Custom Widgets (JavaScript/ARIA).	Required multiple