Label Association Limits in CakePHP 4.x FormHelper Checkbox and Radio Output

CakePHP 4.x projects commonly render entire form fields through FormHelper::control(), and accessibility targets such as WCAG 2.1 AA require every control to have a programmatic label and, where needed, a supporting description. The documented options array accepts attributes like aria-label and aria-describedby, but it is not obvious how much label association the helper performs on its own for checkbox and radio inputs versus what must be configured field by field.

The same uncertainty applies to navigation. Teams need to know whether PaginationHelper emits landmark markup and accessible controls by default, or whether template customization is the only route to compliant pagination. Deciding between per-control options and centralized template overrides depends on where the built-in support actually ends.

Where does default support stop for checkbox and radio label association in CakePHP 4.x, and is the label option required for each control to achieve proper association? Are ARIA attributes passed through the options array rendered directly on the generated input elements? Does PaginationHelper provide a navigation landmark and accessible labels without custom templates?