Review: 3.3.2 Labels or Instructions (A)

[qbalsdon]

Task: Edit MCAG section 3.3.2 considering the mobile research questions (to be completed)

---

Labels or instructions are provided when content requires user input.

Sufficient Techniques for Success Criterion 3.3.2

Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

G131: Providing descriptive labels
    ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls
    ARIA9: Using aria-labelledby to concatenate a label from several text nodes
    ARIA17: Using grouping roles to identify related form controls
    G89: Providing expected data format and example
    G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input
    G162: Positioning labels to maximize predictability of relationships
    G83: Providing text descriptions to identify required fields that were not completed
    H90: Indicating required form controls using label or legend
    [PDF5: Indicating required form controls in PDF forms ](https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF5.html)
H44: Using label elements to associate text labels with form controls
PDF10: Providing labels for interactive form controls in PDF documents
H71: Providing a description for groups of form controls using fieldset and legend elements
[G167: Using an adjacent button to label the purpose of a field ](https://www.w3.org/WAI/WCAG22/Techniques/general/G167.html)

Note: The techniques at the end of the above list should be considered “last resort” and only used when the other techniques cannot be applied to the page. The earlier techniques are preferred because they increase accessibility to a wider user group.

Advisory Techniques for Success Criterion 3.3.2

[G13: Describing what will happen before a change to a form control that causes a change of context to occur is made ](https://www.w3.org/WAI/WCAG22/Techniques/general/G13.html)

Failures for Success Criterion 3.3.2

F82: Failure of Success Criterion 3.3.2 by visually formatting a set of phone number fields but not including a text label