Phalcon Forms component attributes support in version 4.2 shifts ARIA responsibility to developers

Goal

Determine whether Phalcon’s Forms component should automatically generate sensible ARIA attributes (such as aria‑label) for form elements when the optional attributes array is not supplied, preserving backward compatibility while improving out‑of‑the‑box accessibility.

Since version 4.2 introduced the attributes array, developers must manually add ARIA properties; otherwise no ARIA markup is rendered, leaving accessibility to individual implementation and risking inconsistent screen‑reader support.

Should the framework inject a default aria‑label derived from the field’s label or name when attributes are empty? What fallback strategy should be used for elements without a visible label? How can this behavior be configured or disabled per project?