RAWEBA
11.1 Does each form input field have a label?
- WCAG references
- 1.3.1 Info and Relationships (A)
- 2.4.6 Headings and Labels (AA)
- 3.3.2 Labels or Instructions (A)
- 4.1.2 Name, Role, Value (A)
- Techniques
- ARIA6
- ARIA9
- ARIA14
- ARIA16
- F68
- F82
- F86
- G82
- G131
- G167
- H44
- H65
Official methodology to test criterion 11.1
Test 1 (11.1.1)
- Find form fields in the document.
- For each form field, check that the form field
- has a WAI-ARIA
aria-labelledbyattribute referencing an identified passage of text; - has a WAI-ARIA
aria-labelattribute; - is associated with a
<label>element having aforattribute; - has a
titleattribute; - a button adjacent to the form field provides it with a visible label and a visually hidden
<label>element or a WAI-ARIAaria-label,aria-labelledbyortitleattribute provides it with an accessible name.
- has a WAI-ARIA
- If this is the case for a form field, the test is validated.
Test 2 (11.1.2)
- Find the form fields associated with a
<label>element in the document. - For each form field, check that
- The form field has an
idattribute. - The value of the
forattribute of the<label>element is equal to the value of theidattribute.
- The form field has an
- If this is the case for the form field, the test is validated.
Test 3 (11.1.3)
- Find in the document form fields whose label is not visible or nearby (hidden, using the aria-label attribute) or is not attached to the field (using the
aria-labelledbyattribute). - For each form field, check that the form field
- either has a
titleattribute, the content of which makes it possible to understand the nature of the expected input; - is accompanied by a passage of text next to the field which becomes visible when the focus is taken, so that the nature of the expected input can be understood;
- is accompanied by a passage of visible text next to the field, enabling the nature of the expected input to be understood.
- either has a