Martin868
I appreciate you share that information and your genuine interest in OSM. I however have an issue that you are breaking services used by lots of people knowingly, in order to add data that is used in research and maybe a very small subset of disabled people - I doubt many even look at the data you add because there is no tool to do it to speak of. I understand you have to start somewhere if this is a field of interest to you, but there is something in software called backward compatibility. When you build new stuff, the developper have the burden to do it in a way that keeps what is there working. You should have the attitude that whatever you do shall not cause issues to existing users, which are much more numerous. Saying it is up  to the rendering folks to solve it is just too easy. Beside rendering engines are everywhere - phone apps, web sites, dedicated GPS devices such as Garmin, etc. You have the responsibility to make sure you don't break what is there when you start entering you data. You canot just go at it so you can build your labs algorithms  and think the collateral damage is THEIR problem to solve because THEIR is many many people. It cannot work that way. I may repeat myself but I find you are turning the map into a mess with 5 traffic light icons at every corner while 1 is enough, three lines for every street, door icons that get in the ways of POI icons, walking instructions that cannot call street names because they use the "sidewalk" path, etc. In my view you must have a technique that does not create that mess before you go and enter your data. This is YOUR responsibility. This is not my project. However as a dedicated user I don't appreciate you break what I use. Try doing this in Google maps, see if they let you do it.
Don't get me wrong, providing data to disabled people is a fine objective. I don t support the way it is done. Long term I don't think it is viable. A better solution is needed.