Identify common input controls and accessibility requirements for text fields, selects, checkboxes, and radio groups.

• A. Ensure every control has a label, supports keyboard access, accessible names, and group related options with ARIA as needed.
• B. Labels are optional; placeholders are sufficient.
• C. Only text fields need labels; selects and checkboxes can be unlabeled.
• D. ARIA roles are not necessary if controls look accessible.

Answer: (A)

Labeling, keyboard access, and clear naming are essential for form controls. Providing a visible label for every text field, select, checkbox, and radio group ensures assistive technologies can announce the control’s purpose accurately and users understand the form context. Relying on placeholders alone isn’t enough, because placeholders don’t consistently convey meaning once the user starts typing or if the field is empty.

Controls must be reachable and operable with a keyboard, with a logical focus order and visible focus indicators. This guarantees that anyone who uses the keyboard can navigate to and activate each control without a mouse.

Accessible names matter: the name a screen reader reads comes from the label or from an explicit aria-label or aria-labelledby when a visible label isn’t possible. When you have a group of options, like radio buttons, it’s important to convey their relationship as a unit—using a fieldset with a legend or tying the group to a descriptive label via aria-labelledby helps assistive tech announce the group correctly.

ARIA roles should be used to fill gaps only when native HTML semantics don’t provide the needed meaning. If native controls already convey labeling and grouping, extra ARIA roles aren’t necessary; only add ARIA where it helps establish accessible names or groupings for custom or complex controls.