modern browsers allow to propagate the valid/invalid state of native element viasetCustomValidityValidityState APIs.
In combination with css pseudo-selector:invalid this could shrink the size of our lib and the markup changes after validation to a minimum.

we should check whether we can apply our feature set to this api and drop the redundant functionality

see
https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/HTML5/Constraint_validation#Constraint_validation_process

https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/HTML5/Constraint_validation#Constraint_API%27s_element.setCustomValidity()

https://developer.mozilla.org/en-US/docs/Web/API/ValidityState