When implementing checkboxes and radio buttons, which accessibility practices are recommended?

• A. Use custom controls only with aria-checked
• B. Ensure proper labels, group related options with fieldset/legend, accessible state changes, and keyboard operability; use aria-checked if custom controls
• C. Avoid grouping options; rely on default browser behavior
• D. Do not provide keyboard support

Answer: (B)

Ensuring accessibility for checkboxes and radio buttons means making sure everyone can understand and interact with them using a keyboard and assistive technologies. The best practice centers on clear labeling, grouping related options with a fieldset and legend, conveying when a state changes, and preserving keyboard operability. Proper labels link the control to descriptive text so screen readers announce its purpose. Grouping related options with a fieldset and legend helps users understand the scope of the set, such as a radio button group describing what choosing one option means. Reflecting accessible state changes means that, for native controls, the checked state is exposed automatically; if you build custom controls, you should implement the correct ARIA semantics (using role=checkbox or role=radiogroup and updating aria-checked to reflect the current state). Keyboard operability is essential: users should be able to focus controls, toggle with the spacebar, and, for radio groups, move between options with the arrow keys. Using aria-checked is appropriate for custom controls to communicate state, but it must be accompanied by proper labeling, grouping, and keyboard handling. Whenever possible, prefer native inputs, and only rely on custom controls with complete accessibility support.