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

Resolution for ARIA Label Propagation

Based on the provided constraints, you should assume that declarative label configurations from npss 2.x may not propagate reliably in 3.x. Components that utilize a first-class label property (such as standard text fields, checkboxes, and selects) generally continue to generate a <label for="..."> element linked to the control's ID. However, components relying on XML-based labelFor attributes are high-risk, as the new rendering pipeline may ignore these attributes, breaking the accessibility association.

Likely Behavior vs. Confirmed Facts

It is confirmed that the rendering pipeline has changed and that no compatibility matrix exists for label preservation. It is likely (based on general framework patterns) that explicit ARIA attributes (aria-label or aria-labelledby) set via the component API will pass through the pipeline untouched, whereas implicit associations derived from XML attributes are more prone to failure during the 3.x transition.

Migration and Verification Steps

1. Audit XML Views: Identify all components using labelFor. These are the most likely candidates for propagation failure.
2. Implement Automated Accessibility Scanning: To avoid manual DOM inspection across different servlet containers, integrate an accessibility engine like axe-core or pa11y into your CI/CD pipeline.
3. Container-Specific Testing: Since rendering may vary by servlet engine, execute the accessibility suite against a deployed instance of each target container.
4. Verify via Programmatic Assertions: For critical forms, use a headless browser to assert that the input's id matches the for attribute of its associated label.

Legacy Configuration

There is currently no documented configuration flag in npss 3.x to enforce legacy label propagation behavior. If your migration requires this, it must be handled via custom renderers or by updating declarative configurations to the new standard.

Missing Diagnostic Detail: To provide a more specific recommendation on component safety, please specify if you are using a proprietary component extension library or the standard npss core library, as custom renderers may bypass the framework's automatic propagation logic entirely.

Note: Because npss 3.x specific documentation was not provided for verification, these recommendations are based on the provided constraints and general server-side rendering patterns. Please verify against your specific version's release notes.