Gates ignored in route

The algorithm routes through nodes tagged in OSM with barrier=gate. This example route contains two such nodes, at the beginning of Lurvinksteeg and on a track between Kruisdijk and Dinxperlosestraatweg. The nodes were added in november. What’s going on here? Perhaps the OSM data is outdated or this specific tag is ignored because there is no access-related tag?

This issue is rather technical, but it likely stems from a compromise designed to accommodate our primary users—businesses engaged in deliveries, pickups, or on-site services. These users need access to various locations, including those behind gates. We are aware of the concerns and will consider potential adjustments, such as reducing the speed on the track behind the gate to make it less appealing for use.