"Barrier blocking highway" for every crosswalk curb I draw

[une-abeille-osm]

See here for a long list of them: https://osmose.openstreetmap.fr/en/byuser/une%20abeille?level=3

When drawing in sidewalks as separate ways, I draw in curb nodes where the sidewalk meets the crosswalk. This seems to result in an "issue" for every one that I don't set the height for. However, I leave the height out on purpose: to add them on-site with StreetComplete.

It would be good to perhaps ignore barrier=kerb nodes when they connect a crossing to a footpath, since this is not an incorrect type of "barrier" for such a location.

Example of what I mean:

[Famlam]

Item 2130 class 4

I think that the warning is correct, although I can understand that it's a bit inconvenient perhaps for curbs/footways mapped this way.
Imagine crossing left-bottom -> left-top -> right-top. Then on the left-top you would first have to enter the curb, then wait for the traffic lights, then leave the curb again. So you would have two crossings of a curb at different locations.
E.g. like in this picture, where the red dot is where I'd expect curbs and the yellow line is where I'd expect the footways.

[une-abeille-osm]

I don't see why the curb would be in the middle of the crossing way? That is not physical reality. The curb is the point at which sidewalk transitions to the crosswalk.

Would that even affect this error?

[Famlam]

The curb node should indeed be on the position of the curb, I guess my left red dot should've been a mm higher to be more accurate. But still not on the crossing of three ways. As per my example, if you go from left bottom to top right, you are expected to encounter a curb 4x:

1x while leaving left-bottom (1st curb)
1x while entering left-top (via the bottom, 2nd curb)
1x while leaving left-top (via the right, 3th curb)
1x while entering right-top (4th curb)

(Obviously this only holds for curbs as nodes, you could also draw the curb as a way, in that case number 2 and 3 would be the same way, connected to the footways)

Would that even affect this error?

Definitely, just look at the examples on the right of the map view of Osmose after you click a marker. The entire purpose of this check is to find barriers on a connection of highways with more than 2 outgoing directions.

[une-abeille-osm]

There is not really any way to draw the intersection that prevents the issue of a router thinking a curb needs to be traversed when one is crossing multiple directions at once. Sure, in some cases you will be able to skip the curb when doing so (at a four-way stop intersection such as this, for example), but in many cases, once does need to traverse the curb and enter the safety of the sidewalk to wait for a crossing signal to go the other way. I don't believe that this single extra instance of a router thinking a curb needs to be traversed is really a negative thing, given that in many cases you may physically need to do so.

I do draw in multiple footways connecting to the crosswalks when that is the physical reality (see below), but in most cases there is only a single center line between the sidewalk and the curb point at which one would exit the sidewalk. The physical reality in these cases reflects how I have drawn the ways in my original screenshot: regardless of which direction you are crossing, you will go down the center of the curb cut, traverse the curb, then turn to cross the street in one direction or another. It seems odd to be generating thousands of errors for this, especially because it is the accepted OpenSidewalks standard for how to represent this kind of sidewalk configuration.