The update should make it closer to native behaviour:
1) when simple text-based components are provided, the component acts as a single accessibility element with "label", "value" and "hint" filled in
2) when custom components are provided, the component acts as an accessibility wrapper over the existing separate accessibility elements.
The update should make it closer to native behaviour: 1) when simple text-based components are provided, the component acts as a single accessibility element with "label", "value" and "hint" filled in 2) when custom components are provided, the component acts as an accessibility wrapper over the existing separate accessibility elements.
Tested against the app UI tests.