Validation failing for required untranslatable field

Here's the first of two possible approaches. This one skips validation when the element's access is explicitly disabled. Before writing test coverage, I would appreciate some guidance on this approach (vs the next one).

Here's another approach, more to the point, which removes validation for an element that the translation handler should not be on the form.

This applies to more than just date fields.

I have a multilingual D9 site and I had the same issue with an entity reference (media) field, it is an untranslatable and required field. I tested the patch #11 and it worked fine. Thanks @ezeedub.

I noticed that this was fixed on Drupal 10, because while upgrading the site (on another branch) and without the patch we didn't have this issue.

I'm triaging RTBC issues → . I read the IS and the comments.

According to the Issue Summary and #10 and #11 the approach to resolve this has yet to be decided. I also expect that this will need a test.
This also needs to be on 11.x now, changing version.

I am setting this to NR for discussion on the approach to use.

Leaving at RTBC.

Per #14 adding issue summary update and tests.

Moving to NW for the tests.

In my case even the patch will not work with a Media-Element where the image-field is required but not translatable.

I agree with @efrainh's comment in #13
This doesn't seems to be reproducible in latest 11.x.
I even manually tried in 10.2.x branch and doesn't seem to be reproducible there either.

To confirm that, I wrote one simple test case based on steps to reproduce.
Tests are coming green, so probably issue doesn't exist anymore or we need proper steps to reproduce the issue.

One can refer this PR https://git.drupalcode.org/project/drupal/-/merge_requests/7058 for the confirmation of test.