ARIA label propagation inconsistency in form components across npss 3.x upgrade

Version transition impact on accessibility attributes

During migration from npss 2.x to 3.x, automatic ARIA label propagation for form components exhibits inconsistent behavior. The framework's component rendering pipeline changed how label associations are generated, but the migration guide does not specify whether existing declarative label configurations require updates or if the new pipeline handles them automatically.

Constraints and uncertainty

• Component libraries using @FormComponent annotations may render different aria-labelledby or aria-label values depending on container servlet engine.
• XML-based view definitions that explicitly set labelFor attributes might conflict with the new automatic propagation logic.
• No documented compatibility matrix indicates which component types preserve label associations without code changes.

Specific questions

1. Which form component types in npss 3.x reliably propagate ARIA labels from declarative configuration without custom renderers?
2. Does the framework provide a configuration flag to enforce legacy label propagation behavior during incremental migration?
3. How can teams verify label association correctness across servlet containers without manual DOM inspection for each form?