Closed avernet closed 5 months ago
One difference is that the other attributes are generated once and then remain unchanged.
In the case of aria-invalid
and aria-required
, we must add them and remove them dynamically as conditions change.
For this purpose, we must:
Use case: fr:date
when using the native date picker. This might also apply to the non-native case, as in both cases we use an xh:input
with xxf:control="true"
within the XBL component, and the distinction between native/non-native is done in JavaScript.
We automatically add
aria-labelledby
,aria-describedby
, andaria-errormessage
on the element the XBL points to withxxbl:label-for
, but we don't have a similar mechanism for the XForms/XBL engine to add and maintainaria-invalid
andaria-required
.+1 from customer