Same as when a highway crosses another highway, if it crosses a barrier, we want to specify how that happens. IMO most of the time, via a gate. Which could be the one-click-solution.
What are other common node values for such crossings?
Also, the gate that the validator creates could also copy the access keys from the highway. So if the highway access is private, the gate has the same access. At least this is how I always thought the access should be done; I could be double-tagging?

The validation makes sense, I think we should do it.
@tordans there is not only the barrier=gate though, but other types of barrier-entrances as well.
Perhaps an add barrier suggestion, but not quick fix, could be shown
Maybe, this needs to be a bit more defined:
barrier=fence (way),barrier=gate (node)barrier=hedge (way),barrier=entrance (node)Is there a way to see the combinations (and usage stats) of barrier-nodes on the crossing of highway+barrier=fence,hedge,wall,…?
https://taginfo.openstreetmap.org/keys/barrier#values only shows, that barrier=gate is by far the most used of the "opening" keys. But it does not help with stats like we need for the above(?).
It’s important to tag access on barrier nodes when it differs from the way. (You might be allowed to use the driveway on either side of the fence, but the fence itself may be locked – you have to find your way around it.)
By default, OSRM treats these barrier tags as being traversable in the absence of any access tag for driving directions. For walking directions, all barriers are traversable except for these tags; for cycling directions, all are traversable except for these tags.
Most helpful comment
@tordans there is not only the
barrier=gatethough, but other types of barrier-entrances as well.